On Dec 7, 2016 09:13, "Will Parsons" <varro@nodomain.invalid> wrote:
On Tuesday, 6 Dec 2016 5:46 PM -0500, bch wrote: > I've got a collection of files who's apparently only change is the > EXECUTABLE bit set, but after a commit, they're still showing up in "f > chan"; I retried w/ a --sha1sum switch; still listed as changed > (despite the new commit showing up in the "f timel"). touch(1) all the > affected files to bump the timestamp, re-commit, STILL listed as > changed (but an entry in the timeline for that commit is listed). > > Haven't dug further into whats going on, but it looks like an error, > or at least non-intuitive. What kind of filesystem? Apparent dicrepancies in the executable bit can show up if the filesystem doesn't support proper permissions. NetBSD is a fully fledged UNIX... I'm using FFS (fast file system), which is a traditional *BSD filesystem. For completeness' sake, it's FFSv2 with wapbl journaling enabled, but that shouldn't be a factor. I've been using fossil for years in this sort of environment, so curious to find this sort of atypical sticky situation... Happens to not be that serious in this case, but i haven't kludged through it yet, hoping to find out the reason and a fix if applicable. -- Will _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
