git-svn fails different ways depending on svn-remote.svn.url protocol

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm at a complete loss as to what is happening here.  The HTTPS error
that does not allow me to fulfill the commit is:

RA layer request failed: PUT of
'/repository/macports/!svn/wrk/e983e9c6-e86a-4223-b30b-2a7457845272/trunk/dports/perl/p5-params-util/Portfile':
SSL negotiation failed: SSL error: sslv3 alert bad record mac
(https://svn.macports.org) at /opt/local/bin/git-svn line 405

It's pretty consistent but after a few dozen attempts I was able to get
my 10 changes across 10 files committed through a series of commits and
resets until the dcommit was successful.

If I switch the svn url to HTTP, I get something even stranger (I did
create the repository initially from the HTTP URL, but I would hope that
flipping svn-remote.svn.url back and forth between http and https would
be completely transparent) -- however the HTTP version of the error is:

Merge conflict during commit: Your file or directory
'dports/audio/libid3tag/Portfile' is probably out-of-date: The version
resource does not correspond to the resource within the transaction. 
Either the requested version resource is out of date (needs to be
updated), or the requested version resource is newer than the
transaction root (restart the commit). at /opt/local/bin/git-svn line 405

Note that libid3tag/Portfile work was by another committer and about 30
or so commits away from head.  How does one bring this up from being
out-of-date?

I have full transcriptions of the process if this helps, but didn't want
to spam the list with it.

Does anyone have any ideas what might solve either problem?  I think the
former is a Subversion issue because I've heard this complaint from
committers using the svn client... The solution seems to be keep trying
till it takes, which has me shaking my head at the entire process.

I did finally get the commit in through bruteforce via HTTPS, but I lack
confidence in patching any more then a file or two at a time, which is
quite disheartening while trying to follow the philosophy of whole
functional commits and not spread out due to technical deficiencies.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux