svnup is b0rken!
sobomax at freebsd.org
Tue Jun 13 14:51:41 UTC 2017
John, should I drop this into the port as a patch? Approved by: maintainer?
On Mon, Jun 12, 2017 at 4:10 PM, John Mehr <jmehr at umn.edu> wrote:
> It looks like the latest version of Subversion has become more strict with
> regards to CR+LFs and the attached patch should get things working for you
> again. Please give it a try and let me know how it goes.
> I've got a couple other fixes I'm working on and I'm hoping to have 1.08
> rolled out in the next week or so. I used to host the tarball on my
> personal web server (which due to an ISP change is no longer available) and
> I'm looking into finding a new place to host it (probably github).
> On Mon, Jun 12, 2017 at 1:03 PM, Maxim Sobolev <sobomax at freebsd.org>
>> Hi, latest version of the svnup package is broken on several of my boxes.
>> I've tried few public svn mirrors makes no difference.
>> [sobomax at van01 ~/projects/softswitch]$ svnup ports
>> # Revision: 443456
>> Command Failure: HTTP/1.1 400 Bad Request
>> Date: Mon, 12 Jun 2017 18:01:09 GMT
>> Server: Apache
>> Connection: close
>> Content-Type: text/html; charset=iso-8859-1
>> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
>> <title>400 Bad Request</title>
>> <h1>Bad Request</h1>
>> <p>Your browser sent a request that this server could not understand.<br
> John Mehr
> Software Developer / Database Administrator
> Humphrey School of Public Affairs, University of Minnesota
More information about the freebsd-ports