gitup: process_command: read failure

There was svn and svnup.
Then there was git, which initially had ± 86 dependencies - to only do a few HTTP requests.
And so again a lite version arrived on the horizon: gitup.
(which I prefer above doing more maintenance than actual useful utilising).

A repo that's messing up clients isn't exclusive to neither git or gitup.
But when a server acts unexpected, should we then blame the client?
(intended as retorical/philosophical question - but feel free to go wild on it).

Regardless,
to upgrade the gitup port, while being unable to run gitup ports to update /usr/ports, I did this:


cd /usr/ports/net/gitup/
make extract
fetch -o work/gitup-1.0/gitup.c \
https://raw.githubusercontent.com/johnmehr/gitup/38090aa09cba27664e524ecd9cabfeb2515bc579/gitup.c
make deinstall
make reinstall



After that gitup can handle the unexpected behaviour of webservers.
 
This worked. Thank you. I did find that after doing it, I had to run git up twice. The message was something had been moved, please run gitup again. I didn't think to copy it, which was careless on my part.

One the machine that I already switched to using git, I may leave things alone since, as fernandel mentioned, it does seem much faster.
 
You must log in or register to reply here.
Back
Top