Re: [fossil-users] EXECUTABLE, and not really being added to updated repo
On Wed, Dec 07, 2016 at 12:13:01PM -0500, Will Parsons 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. > Also, might be slightly related. On windows (using binary from download page: mingw 32bit), the EXECUTABLE bit seems to be ignore on the checkout and even if the filesystem don't support permissions, "fossil change" doesn't see any mismatch on the EXEC bit. Probably because of those check: http://fossil-scm.org/index.html/artifact?ln=1550+1563&name=1913859177ca9012 http://fossil-scm.org/index.html/artifact?ln=249+256&name=0cd782064e70a543 This check if current architecture support executable bits, but *not* if the actual *filesystem* support it. Moreover, it use _WIN32. So if I produce a 64bit windows executable using mingw-w64 (from msys2: https://msys2.github.io/), _WIN32 is not defined and "fossil change" always report a bunch of UNEXEC/EXEC changes on NTFS or FAT filesystem. I don't know if it's related with your problem, but I think there's something to improve here, I'm not sure yet what is best way to handle this ? May be a new setting to ignore permission can be useful, which can be set differently on different checkout. Regards, -- Martin G. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] EXECUTABLE, and not really being added to updated repo
On Dec 7, 2016 09:13, "Will Parsons" 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
Re: [fossil-users] EXECUTABLE, and not really being added to updated repo
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. -- Will ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] EXECUTABLE, and not really being added to updated repo
On Dec 6, 2016 19:18, "Andy Bradford" wrote: Thus said bch on Tue, 06 Dec 2016 14:46:23 -0800: > 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). I haven't been able to reproduce this. What version of Fossil? Hey Andy. Tip of trunk, then jumped back in time to May 2014 in a few different steps... I'll have to dig in a bit more. Given the revisions I've tried (going to find a regression by bisecting), it really does seem pretty curious now. Will have to properly characterize what's going on. On NetBSD (amd64), -current, fwiw. -bch Here's what I did: $ fossil new test.fossil project-id: 8763c2afcfc0adca5366be5f53225459f15c63b4 server-id: 0f0cb472cf82d3dd772996a526a5d69072ffb726 admin-user: amb (initial password is "19e0e7") $ fossil open test.fossil project-name: repository: /tmp/test.fossil local-root: /tmp/ config-db:/home/amb/.fossil project-code: 8763c2afcfc0adca5366be5f53225459f15c63b4 checkout: 01f3812d6588d5dc8a1f396d1698336009f36bde 2016-12-07 03:16:02 UTC tags: trunk comment: initial empty check-in (user: amb) check-ins:1 $ echo $RANDOM > file $ ls -l file -rw-r--r-- 1 amb wheel 6 Dec 6 20:16 file $ fossil add file ADDED file $ fossil ci -m no-execute New_Version: 1fc3e40325e5fa0e91f7f634f021e2ce840ef9c2 $ chmod 755 file $ fossil changes EXECUTABLE file $ fossil ci -m execute New_Version: db9e561227ae4431b5eff542ac3cea278bb48817 $ fossil time === 2016-12-07 === 03:16:40 [db9e561227] *CURRENT* execute (user: amb tags: trunk) 03:16:28 [1fc3e40325] no-execute (user: amb tags: trunk) 03:16:02 [01f3812d65] initial empty check-in (user: amb tags: trunk) +++ no more data (3) +++ $ ls -l file -rwxr-xr-x 1 amb wheel 6 Dec 6 20:16 file* Andy -- TAI64 timestamp: 400058477fc4 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] EXECUTABLE, and not really being added to updated repo
Thus said bch on Tue, 06 Dec 2016 14:46:23 -0800: > 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). I haven't been able to reproduce this. What version of Fossil? Here's what I did: $ fossil new test.fossil project-id: 8763c2afcfc0adca5366be5f53225459f15c63b4 server-id: 0f0cb472cf82d3dd772996a526a5d69072ffb726 admin-user: amb (initial password is "19e0e7") $ fossil open test.fossil project-name: repository: /tmp/test.fossil local-root: /tmp/ config-db:/home/amb/.fossil project-code: 8763c2afcfc0adca5366be5f53225459f15c63b4 checkout: 01f3812d6588d5dc8a1f396d1698336009f36bde 2016-12-07 03:16:02 UTC tags: trunk comment: initial empty check-in (user: amb) check-ins:1 $ echo $RANDOM > file $ ls -l file -rw-r--r-- 1 amb wheel 6 Dec 6 20:16 file $ fossil add file ADDED file $ fossil ci -m no-execute New_Version: 1fc3e40325e5fa0e91f7f634f021e2ce840ef9c2 $ chmod 755 file $ fossil changes EXECUTABLE file $ fossil ci -m execute New_Version: db9e561227ae4431b5eff542ac3cea278bb48817 $ fossil time === 2016-12-07 === 03:16:40 [db9e561227] *CURRENT* execute (user: amb tags: trunk) 03:16:28 [1fc3e40325] no-execute (user: amb tags: trunk) 03:16:02 [01f3812d65] initial empty check-in (user: amb tags: trunk) +++ no more data (3) +++ $ ls -l file -rwxr-xr-x 1 amb wheel 6 Dec 6 20:16 file* Andy -- TAI64 timestamp: 400058477fc4 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] EXECUTABLE, and not really being added to updated repo
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. -bch ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users