- removed comment
The mojave variable "thornlist" cannot deal with absolute path names; update repo fails then...
Issue #730
closed
Using Eclispe (indigo classic), I have tried to build with a new thornlist.
Therefore I have entered the following name in
mojave -> edit variables
/home/alibeck/Cactus-Simfact2-NewRepos-save/Cactus/test-ali.th
Staring then "update repo"
gives me:
[1m[31mError: [0mCould not open Cactus//home/alibeck/Cactus-Simfact2-NewRepos-save/Cactus/test-ali.th
So mojave tries to open a file called
Cactus//home/alibeck/Cactus-Simfact2-NewRepos-save/Cactus/test-ali.th
instead of
/home/alibeck/Cactus-Simfact2-NewRepos-save/Cactus/test-ali.th
Keyword:
Comments (6)
-
-
- removed comment
From the ticket description, it looks like there is a trivial workaround, so I don't see how it could be a "blocker". I suggest that it be demoted to "minor".
-
- removed comment
Mojave is a live project, but somehow we've not gotten into the spirit of using Trac. Will look into it.
-
reporter
- removed comment
If the user opens the .mojave.xml file inside the Cactus source tree in the project, the parameter that following the --update is currently written as Cactus/ and if you delete the Cactus/ then this option would work.
-
reporter
- changed status to resolved
- removed comment
If the user opens the .mojave.xml file inside the Cactus source tree in the project, the parameter that following the --update is currently written as Cactus/ and if you delete the Cactus/ then this option would work. For the future checkouts, I will rewrite the .mojave.xml file. I don't have permission to rewrite the file. I will request Steve to change the file.
-
- edited description
- changed status to closed
- Log in to comment
This is the most serious ticket open, and has been open for seven months. Is Mojave a dead project? Or is this ticket's priority wrong? Or has this issue already been addressed?