{"thread":{"id":"8763","subject":"git-svn fails different ways depending on svn-remote.svn.url protocol","startedAt":"2007-06-28T18:05:44Z","lastAt":"2007-06-28T18:05:44Z","messageCount":1,"participants":["Mark Grimes"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"45995","messageId":"y59sLxMx.1183053944.4686070.mgrimes@harwood.textdrive.com","threadId":"8763","inReplyTo":null,"subject":"git-svn fails different ways depending on svn-remote.svn.url protocol","fromName":"Mark Grimes","fromEmail":"mark@stateful.net","sentAt":"2007-06-28T18:05:44Z","receivedAt":"2007-06-28T18:05:44Z","isPatch":false,"sender":{"key":"mark@stateful.net","avatar":null},"body":"I'm at a complete loss as to what is happening here.  The HTTPS error\nthat does not allow me to fulfill the commit is:\n\nRA layer request failed: PUT of\n'/repository/macports/!svn/wrk/e983e9c6-e86a-4223-b30b-2a7457845272/trunk/dports/perl/p5-params-util/Portfile':\nSSL negotiation failed: SSL error: sslv3 alert bad record mac\n(https://svn.macports.org) at /opt/local/bin/git-svn line 405\n\nIt's pretty consistent but after a few dozen attempts I was able to get\nmy 10 changes across 10 files committed through a series of commits and\nresets until the dcommit was successful.\n\nIf I switch the svn url to HTTP, I get something even stranger (I did\ncreate the repository initially from the HTTP URL, but I would hope that\nflipping svn-remote.svn.url back and forth between http and https would\nbe completely transparent) -- however the HTTP version of the error is:\n\nMerge conflict during commit: Your file or directory\n'dports/audio/libid3tag/Portfile' is probably out-of-date: The version\nresource does not correspond to the resource within the transaction. \nEither the requested version resource is out of date (needs to be\nupdated), or the requested version resource is newer than the\ntransaction root (restart the commit). at /opt/local/bin/git-svn line 405\n\nNote that libid3tag/Portfile work was by another committer and about 30\nor so commits away from head.  How does one bring this up from being\nout-of-date?\n\nI have full transcriptions of the process if this helps, but didn't want\nto spam the list with it.\n\nDoes anyone have any ideas what might solve either problem?  I think the\nformer is a Subversion issue because I've heard this complaint from\ncommitters using the svn client... The solution seems to be keep trying\ntill it takes, which has me shaking my head at the entire process.\n\nI did finally get the commit in through bruteforce via HTTPS, but I lack\nconfidence in patching any more then a file or two at a time, which is\nquite disheartening while trying to follow the philosophy of whole\nfunctional commits and not spread out due to technical deficiencies.\n"}]}