From: Klemens Nanni <kn@openbsd.org>
Subject: Re: Update devel/github-cli port to version 2.83.2
To: David Uhden Collado <daviduhden@gmail.com>, ports@openbsd.org
Date: Thu, 08 Jan 2026 17:40:16 +0000

07.01.2026 20:07, David Uhden Collado пишет:
> Hello all,
> 
> Attached to this email is a patch that updates the devel/github-cli port from version 2.79.0 to 2.83.2.

How did you update the port?

When I run the following, which is how I've been updating the g*-cli
ports all the time, recent versions started failing to fetch:

	# fetch new version without modules
	>| modules.inc
	make makesum
	make extract

	# update and fetch (new) modules
	make modgo-gen-modules >| m
	mv m modules.inc
	make makesum -j$(make show=MAKE_JOBS)

	# build and test
	make build
	make update-plist
	make update


===>  Checking files for github-cli-2.83.2
>> Fetch https://proxy.golang.org/github.com/go-openapi/swag/jsonutils/@v/v0.0.0-00010101000000-000000000000.mod
ftp: Error retrieving https://proxy.golang.org/github.com/go-openapi/swag/jsonutils/@v/v0.0.0-00010101000000-000000000000.mod: 404 Not Found
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:3310 '/usr/ports/distfiles/go_modules/github.com/go-openapi/swag/jsonutils/@v/v0.0.0-00010101000000-000000000000.mod')
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2531 '_internal-fetch-all': @cd /p/devel/github-cli && PKGPATH=devel/github-cli e...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2710 'fetch-all': @lock=github-cli-2.83.2;  export _LOCKS_HELD=" github-cli-2.83....)
*** Error 2 in /p/devel/github-cli (/usr/ports/infrastructure/mk/bsd.port.mk:2346 'makesum': @make fetch-all _MAKESUM=true)

In-tree 2.79.0 does not exhibit this failure, so it must be some
upstream change.  Back then the first release after that came out
I briefly looked into it, but did not find the culprit.

From then on so far I just checked newer versions and hoped for
it to fix itself...

> 
> I have tested this update on the amd64 platform and everything appears to work correctly overall. The only exception is the interactive authentication via gh auth login, which is still not functioning; however, this issue was already present prior to the update. It would be worthwhile to investigate a way to fix this in the future.

Is this an auth-specific problem or are you about interactive input?

Afaict, the problem with prompts (same for gitlab-cli) came with our
syscalls changes that broke the module doing the work;  however,
I did not check which module exactly or what it does now.

> 
> I look forward to any feedback or suggestions.
> 
> Best regards,
> David.