Re: net/gitup began to fail

Whoops, sorry, a tragic copy-and-paste mishap caused the "295067" link 
to actually be just another link to 295065. Here is the real 295067 
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295067> (I hope).

On 5/7/2026 1:17 AM, Robert William Vesterman wrote:
> This is happening to me too, and others. Here are some links I've been 
> checking regarding it:
>
> FreeBSD Forums: gitup: process_command: read failure 
> <https://forums.freebsd.org/threads/gitup-process_command-read-failure.102614/>
> Bugzilla: 295065 
> <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295065>, 295066 
> <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295066>, and 295067 
> <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295065>
> FreeBSD Hackers mailing list: gitup failure 
> <https://lists.freebsd.org/archives/freebsd-hackers/2026-May/006223.html>
>
> The FreeBSD Hackers link is to the top email in the thread. 
> Unfortunately I don't know see any way to easily navigate a thread 
> (like, I don't see a "Next in Thread" link). I've been occasionally 
> checking the May 2026 by-thread archive 
> <https://lists.freebsd.org/archives/freebsd-hackers/2026-May/index.html> and 
> just manually checking the links to individual messages in the thread.
>
> I don't really understand why there are three separate Bugzilla 
> reports. They're all by the same person, who is also the person who 
> started the thread in the FreeBSD Hackers mailing list. He gave an 
> explanation in the FreeBSD Forums thread, but it was pretty terse and 
> I get the feeling that I might have misinterpreted it.
>
> To be clear, there is currently (well, last I checked) nothing in any 
> of these things I linked to that seems particularly useful in a direct 
> way to end users who are having the issue; just reports that it's 
> happening. But I imagine that eventually something will get to one or 
> more of these.
>
> On 5/7/2026 12:44 AM, [email protected] wrote:
>> I successfully used port net/gitup to update ports tree. Suddenly it began
>> to fail. I deleted /usr/ports and told gitup to clone it - same error
>> (on both my hosts - workstation and VPS):
>>
>> ~ # gitup -c ports
>> # Host: git.freebsd.org
>> # Port: 443
>> # Repository Path: /ports.git
>> # Target Directory: /usr/ports
>> # Want: 10584ee144da9593c353e500874e0683bcc2833f
>> # Branch: main
>> gitup: process_command: read failure:
>>
>> HTTP/1.1 200 OK
>> Server: nginx/1.28.3
>> Date: Thu, 07 May 2026 04:36:33 GMT
>> Content-Type: application/x-git-upload-pack-result
>> Transfer-Encoding: chunked
>> Connection: keep-alive
>> Expires: Fri, 01 Jan 1980 00:00:00 GMT
>> Pragma: no-cache
>> Cache-Control: no-cache, max-age=0, must-revalidate
>> 0011shallow-info
>> 0001000dpackfile
>> 00052004PACK
>> : Invalid argument
>> ~ #
>>
>> Debug with "-v 3" doesn't show more info.
>> 14.4-RELEASE-p3 amd64.
>>
>