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.
 
Maybe fixed by commit ports 287d1cb968820903e27d433af3b8883e828d0796 on latest (aka main).
Would need 3 days (or more) to be MFH'ed to 2026Q2 (quarterly).

For anyone using gitup to update ports tree and don't installed devel/git and don't want to use official pkg with some reason (so assume your port tree still has 1.0),
  1. Download the patch mentioned at Comment 12 of PR 295067 into somewhere you want,
  2. cd to /usr/ports/net/gitup
  3. Run make extract
  4. cd to /usr/ports/net/gitup/work/gitup-1.0
  5. Apply it with patch -p1 -i /path/to/the/patch/38090aa09cba27664e524ecd9cabfeb2515bc579.patch
  6. Run make && make deinstall && make reinstall
may help.
To be a bit paranoid, do dry-run between step 4 and 5 with adding option -n.
 
fernandel, I ran gitup after trying dns.company's fix and it gave a message, the one I didn't keep, I think it was something about something being moved, anyway, it then read please rerun gitup. Which I did (gitup ports), and everything was normal, it ran a typical gitup session.
 
You must log in or register to reply here.
Back
Top