-
Notifications
You must be signed in to change notification settings - Fork 55
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
Problem replicating the "Using Gin as a data source behind the scenes" walkthrough #779
Comments
(Image: CC-BY license, The Turing Way Community, & Scriberia. Zenodo. http://doi.org/10.5281/zenodo.3332808) Hi there, and welcome to the DataLad Handbook! 📙 👋 Thank you for filing an issue. We're excited to have your input and welcome your idea! 😊 If you haven't done so already, please make sure you check out our Code of Conduct. |
Huh, now I cannot replicate my own problem... I'll go through it once more tomorrow, checking my bash history, but it seems that the sample code is fine and the description is also correct. |
Sounds good! |
For the record, it seems that the That being said, in a private repository and without |
I am still at a loss here. Private repo. The
... and I'm able to follow through with the following steps:
But then, in a clone made from github, the
There is a trace of the gin repository being recorded:
But the clone does not have any remotes other than its GitHub origin:
(not sure if relevant, but also note - above - that the source repository only had one remote, |
making a note of a comment with a todo: datalad/datalad#6204 (comment) |
Suggested add - push - configure - push as a correct sequence. Addresses #779
Current behavior
I tried to follow the Using Gin as a data source behind the scenes walkthrough from Chapter 8.6 (Dataset hosting on GIN) verbatim, but didn't succeed. There is an error when configuring the gin remote as a common data source, which I don't know how to correct. If I ignore it and carry on, the dataset gets pushed to GitHub & Gin, but without the link between the two (i.e. getting from GitHub clone doesn't work). Commands and their outputs below.
As a side note - I assume that the git + gin part of the walkthrough is meant to be stand-alone (starts by creating a new repository on Gin & uses different repo names than the examples before). If, however, the steps depends on some previous configuration, then the wording might need tweaking.
Operating system
Debian GNU/Linux 11 (bullseye)
DataLad information
Datalad version 0.15.0
Git annex version 8.20210903-1~ndall+1
Browser
No response
Additional context
The git annex error from
datalad siblings add -d . --name gin-update ... --as-common-datasrc gin
says "could not find existing git remote with specified location". But that doesn't mean that I need to configure something previously, right? I'd expect the command to do the configuration.Coincidentally, I also ran into the same error message in a completely separate dataset and usecase, when I experimented with
git annex initremote
(to change a local remote into a special one). So that might be something to do with my setup, but I think that one was replicated by another person.The text was updated successfully, but these errors were encountered: