It sounds similar indeed. One thing that is perhaps worth mentioning is
that rm works just fine if you do it before you delete the actual file.
Another thing is that addremove did report that the file was deleted,
but then it was still reported missing by status and commit. I'll update
the ticket with that information in the morning.
Kind regards,
Philip Bennefall
On 9/13/2014 6:17 AM, B Harder wrote:
I haven't had time to dig in, but that sounds like the ticket I opened
this week. If it sounds like that to you too, kindly add any more
relevant info you have:
http://fossil-scm.org/index.html/tktview?name=94a1f83f9f
On Sep 12, 2014 9:12 PM, "Philip Bennefall" <[email protected]
<mailto:[email protected]>> wrote:
Hi all,
I am running a build of Fossil that is newer than the last public
release, though I cannot remember exactly what check-in it is. I
am having a bit of trouble with addremove. I remove the files in
question from the repository and then I run addremove, and get the
expected output which says deleted something.xyz. Then I run
fossil commit, but it fails with a complaint about missing files.
If I then say revert, and then use fossil rm to get rid of the
files manually, status reports the files as deleted rather than
missing. I don't recall having any issues with this in prior
versions of Fossil. Am I doing something wrong in my workflow or
is this potentially a bug?
Kind regards,
Philip Bennefall
_______________________________________________
fossil-users mailing list
[email protected]
<mailto:[email protected]>
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
