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

VCS control with git does not work (requirement file not found) #28

Open
dav1d-wright opened this issue Jan 23, 2019 · 1 comment
Open

Comments

@dav1d-wright
Copy link

dav1d-wright commented Jan 23, 2019

When I switch from filesystem access method to git, as described in the manpage rmtoo-config3 there seems to be some issue with the paths to the requirement files.

This is a snippet of my config file:

"topics": {
    "ts_common": {
    "sources": [
        [
	    "git", {
            "start_vers": "f2dc410bb3cc7bec9c090d6c4f1433f092790058",
            "end_vers": "HEAD",
	        "requirements_dirs": [ "requirements" ],
			"topics_dirs": [ "topics" ],
			"topic_root_node": "ReqSpec",
			"constraints_dirs": [ "constraints" ]}
	] 

When I try to build the requirement spec, I get the following error:

make[1]: *** No rule to make target `doc/ReqSpec/requirements/project.req', needed by `artifacts/reqtopics.tex'.  Stop.

As soon as I switch from "git" to "filesystem" and remove "start_vers" and "end_vers" it works as desired. Does rmtoo have issues with the rmtoo project being located in a subfolder of the git repository?

Edit
If I modify the "requirement_dirs" parameter in the Config.json file to represent the relative path to the git-root directoriy, it gives me the following error

+++ ERROR: Problem reading in the continuum [[ 108]: directory entry [doc] not found in tree [ReqSpec].]
@florath
Copy link
Owner

florath commented Jan 24, 2019

Can you please check, that the file project.req is available in the referenced versions?

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

No branches or pull requests

2 participants