Comments:
|
Date: 2014-04-03 17:43 Sender: A. Marcia BarbosaAhaa, so that's what you meant by "explicitly add new files"! I know these things may sound incredibly obvious to those in the know, but for self-taught users with no informatics background, such little details are plain enigmas. Thanks a lot for your detailed instructions, this time the Linux terminal did acknowledge the adding and committing of the files. The project summary page on R-Forge still says "0 commits, 0 adds", but I figure there's a normal time lag. Hopefully my package will finally be online tomorrow...
The manual does seem to assume familiarity with svn, but this may not be so common among users with different backgrounds, and reading (and understanding...) the svn manual would just be another huge mountain for us to climb. Adding just a few lines mentioning the "svn add" and "svn commit" to the R-Forge manual could spare many people many problems in the future. In fact I think I'll write those lines myself and send them to the authors of the manual to be considered for a future revision.
Again, thanks a lot! Hopefully this will do it! | Date: 2014-04-03 16:50 Sender: Martin PacalaWell the manual assumes one is familiar with the use of svn as far as I know. But I'm glad that we have some progress. Now all you still need to do is to do '$svn add filename' before doing '$svn commit'. Commit only checks for modified files, but you need to use add or delete for adding or removing new files as a whole. Only after you add a file can you then commit it and it will be added into the svn repo. I think that should get you running | Date: 2014-04-03 16:11 Sender: A. Marcia BarbosaMany thanks for your quick reply. That's right, I hadn't committed - there's no mention of that in the R-Forge manual... Anyway I googled "svn commit" and I've done it now ('svn commit fuzzysim/pkg' in the Linux terminal), but there's no sign that anything really happened -- it did not launch an editor for me to compose a commit message, nor did the terminal show any response (something like 'Sending file; Transmitting file data; Committed revision 1') when I committed again, this time adding the message on the command line itself (svn commit -m "added package files"). Also, the project summary page on R-Forge still says "Subversion: 0 commits, 0 adds". Is this normal and do I just have to wait overnight to see any result, or am I still stuck?
Thanks again for any extra help! | Date: 2014-04-03 14:21 Sender: Martin PacalaOk I think you actually didn't commit anything yet. After you check something out, you need to explicitly add new files and then commit all changes. only after you make the commit will the modified files get uploaded and r-forge can build your package on the next run | Date: 2014-04-03 11:35 Sender: Martin PacalaI'm looking into this, I can reproduce the error but can't really see why it's happening. |
|