Re: [fossil-users] artifacts received
Richard Hipp wrote about this before: https://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg11761.html His reponse in that link: The pull and sync are requesting and receiving all SHUN records. You can disable this using fossil setting auto-shun off On Sun, Jul 6, 2014 at 3:10 PM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said B Harder on Sun, 06 Jul 2014 14:40:58 -0700: myhost$ fossil pull http://joeb...@fossil-scm.org --http-trace Round-trips: 1 Artifacts sent: 0 received: 0 Pull finished with 424 bytes sent, 612 bytes received It seems that I gave you the wrong option. Please try: fossil pull --httptrace Andy -- TAI64 timestamp: 400053b9c98a ___ 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] artifacts received
That looks to be the end of this mystery. For those wondering why do we request the same shun artifacts over and over and over and...: == The fact that the shunning list does not propagate is a security feature. If the shunning list propagated then a malicious user (or a bug in the fossil code) might introduce a shun record that would propagate through all repositories in a network and permanently destroy vital information. By refusing to propagate the shunning list, Fossil insures that no remote user will ever be able to remove information from your personal repositories without your permission. == Thanks Andy, Ron, Stephan, Donny. -bch On 7/7/14, Donny Ward donnyjw...@gmail.com wrote: Richard Hipp wrote about this before: https://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg11761.html His reponse in that link: The pull and sync are requesting and receiving all SHUN records. You can disable this using fossil setting auto-shun off On Sun, Jul 6, 2014 at 3:10 PM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said B Harder on Sun, 06 Jul 2014 14:40:58 -0700: myhost$ fossil pull http://joeb...@fossil-scm.org --http-trace Round-trips: 1 Artifacts sent: 0 received: 0 Pull finished with 424 bytes sent, 612 bytes received It seems that I gave you the wrong option. Please try: fossil pull --httptrace Andy -- TAI64 timestamp: 400053b9c98a ___ 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] artifacts received
On Mon, Jul 7, 2014 at 10:10 PM, B Harder brad.har...@gmail.com wrote: Fossil insures that no remote user will ever be able to remove Shouldn't that be ensures? i always confuse the two. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ 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] artifacts received
Good catch: you're correct. -bch On 7/7/14, Stephan Beal sgb...@googlemail.com wrote: On Mon, Jul 7, 2014 at 10:10 PM, B Harder brad.har...@gmail.com wrote: Fossil insures that no remote user will ever be able to remove Shouldn't that be ensures? i always confuse the two. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ 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] Update config.* in autosetup directory?
On Sat, Jun 21, 2014 at 9:11 PM, Joe Prostko joe.pros...@gmail.com wrote: I was just trying to build Fossil on the x86-64 version of Haiku, and it didn't get far since the platform failed to be identified. I replaced the versions of config.guess and config.sub shipped with Fossil and then configure worked, as well as the rest of the build. Is there any chance those two files can be updated? They are available at the following links: config.guess: http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD config.sub: http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD Hey, I am just replying to this mail in case it didn't get noticed the first time around. If config.sub and config.guess could be updated to something more recent before Fossil 1.30 comes out, that would be appreciated. If there is a reason to stay with the older versions of those files, I will be happy to supply a patch to have support for Haiku x86-64. Just let me know. Thanks! - joe ___ 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] artifacts received
Thus said Donny Ward on Mon, 07 Jul 2014 12:56:03 -0700: His reponse in that link: The pull and sync are requesting and receiving all SHUN records. I'm not sure that this is what is happening in this case. The --httptrace output only showed 3 gimme cards requested and none of them are on the SHUN list. Also, the received count only increments for file, cfile and config cards if I'm not mistaken, so the data that comes in as part of the unclustered artifacts will not count for it. Andy -- TAI64 timestamp: 400053bb05f5 ___ 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] Update config.* in autosetup directory?
Joe Prostko wrote: Is there any chance those two files can be updated? They are available at the following links: config.guess: http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess ;hb=HEAD config.sub: http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;h b=HEAD I've updated them on the 'pending-review' branch. These changes, which look fairly extensive, are going to need wider review (and possibly more testing) before being merged to trunk. Hopefully, this will be completed well before the release of 1.30. -- Joe Mistachkin ___ 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] Update config.* in autosetup directory?
On Mon, Jul 7, 2014 at 5:03 PM, Joe Mistachkin sql...@mistachkin.com wrote: Joe Prostko wrote: Is there any chance those two files can be updated? They are available at the following links: config.guess: http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess ;hb=HEAD config.sub: http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;h b=HEAD I've updated them on the 'pending-review' branch. These changes, which look fairly extensive, are going to need wider review (and possibly more testing) before being merged to trunk. Hopefully, this will be completed well before the release of 1.30. Thank you, Joe! And yes, keep the changes in the pending-review branch until you are sure everything is safe to merge. Like you, I would prefer things be done right, so there's definitely no rush. Thanks again. - joe ___ 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] artifacts received
Thus said Andy Bradford on 07 Jul 2014 14:40:51 -0600: I'm not sure that this is what is happening in this case. The --httptrace output only showed 3 gimme cards requested and none of them are on the SHUN list. Ok, apparently the --httptrace that was sent was not representative of the problem reported. I have been able to reproduce it and indeed it is due to receiving config data for shunned artifacts in the response. Included in the request was: reqconfig /shun And of course in the response: config /shun 63 1305210229 '0335363c1394804c7c9677842ddc81889d1e18b1' scom NULL config /shun 63 1305210229 '093ff6aedd0832beb6dc09e86606ea05e0ef42b5' scom NULL config /shun 63 1305210229 '0a838c29e8ba80fa9cb4e68c316e7f1a568e9eca' scom NULL $ grep -c '^config' http-reply-1.txt 74 Thanks Donny for digging up this information from the mailing list archive. Andy -- TAI64 timestamp: 400053bb3045 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
