|
I've used the "vv addremove" command a lot and I like it. It is much easier than hunting everything down and adding them all by hand. I have just gone through a pull, merge, resolve, commit, ... series of steps to pull in some conflicting changes. At this point, when I do a vv status I see a lot of files that need to be added. However, when I do vv addremove, none of them get added. vv status still shows them all as "Found". Are there times when vv addremove won't add Found files? I've checked vv heads and there is only one head in my local repository. I haven't yet done a push to the master, but I'll try that next and see if addremove starts working again. Any suggestions welcome. Some output from my working directory and actions: smc@smcdesk ~/dev/vc/Client/hub/src/logic/ascfg
$ vv status
Modified: @/Client/hub/src/logic/utils/Makefile.msvc
Modified: @/Client/hub/src/logic/utils/UserProperties.cpp
Lost: @/Client/hub/src/logic/ascfg/ViaEnvironment.cpp
Lost: @/Client/hub/src/logic/ascfg/ViaEnvironment.h
Lost: @/Client/hub/src/logic/ascfg/ViaEnvironment.sql.xml
Lost: @/Client/hub/src/logic/dash/ViaservEnv.cpp
Lost: @/Client/hub/src/logic/dash/ViaservEnv.h
Lost: @/Client/hub/src/logic/dash/ViaservEnv.sql.xml
Found: @/Client/hub/src/logic/utils/ViaservEnv.cpp
Found: @/Client/hub/src/logic/utils/ViaservEnv.h
Found: @/Client/hub/src/logic/utils/ViaservEnv.sql.xml
That time, it recognized 3 of the "Lost" files and marked them as removed. But not all of the lost files, and none of the Found files. I'm going to try the vv scan option next, as suggested, and see if it helps things. ... Here's the process with using vv scan: smc@smcdesk ~/dev/vc/Client/hub/src/logic/ascfg $ vv scan It doesn't look like vv scan helped anything here. ... Trying with vv addremove at the root level with a folder name option: smc@smcdesk ~/dev/vc $ vv addremove Client Looks like that did the trick! So why would addremove behave differently for the 2 different scenarios? Seems like a bug to me :-) |
|
The 'addremove' command should always add anything that it finds. I'm not sure what could be causing the problem you're seeing. Is it possible that the items are inside an ignored directory or do you have anything in a .vvignores file that could confuse it? Does a plain 'vv add' on one of the found items, work? I do have a .vvignores file, but that is working properly. i.e. anything in the ignores does not show up when I do "vv status". Only the new stuff shows up with "vv status". What I've done is to copy the output of "vv status" into a script where I change the "Found: @/" beginning of each line to "vv add ". I then run the script and all of the manual vv add commands work just fine.
(Jan 31 at 10:58)
smc314
My system did crash over the weekend (unrelated to veraciy). Would/could that have affected the internal state of veracity to the point where addremove does not work but status, add, commit, pull, push all do work?
(Jan 31 at 12:30)
smc314
1
The crash shouldn't matter (unless maybe if the crash happened during a vv operation, but i doubt that's what you're seeing). I'm not sure why addremove isn't working for you. Next time it happens, try doing a 'vv scan' and then a 'vv status' and then retry the addremove. (Scan is like status, but it flushes some caches first.) Another thing to try is to see if it matters if you do the addremove from the top of the working directory (with no args) vs doing an addremove with a file/folder argument.
(Jan 31 at 13:35)
Jeff Hostetler ♦♦
I tried vv scan (see above expanded description) I'll try it from the root directory with a foldername option next.
(Jan 31 at 14:56)
smc314
Using addremove at the root level with a foldername argument did the trick. Thanks for helping me through the options. I've put all of the input/output above so that hopefully it will help identify/squash whatever bug is at work here.
(Jan 31 at 15:01)
smc314
1
Yeah, that sounds like a bug. I'll log it. Thanks for your patience.
(Jan 31 at 15:23)
Jeff Hostetler ♦♦
showing 5 of 6
show all
|
