github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Building 1.18.5 not successful for go.jolheiser.com modules #13222

New Issue
Closed
opened 2025-11-02 10:35:23 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 10:35:23 -06:00
Owner
Copy Link

Originally created by @zcopado on GitHub (Jul 1, 2024).

Description

Upon attempting to build the docker image for gitea v1.18.5, it fails as follows:

420.2 go: downloading go.jolheiser.com/pwn v0.0.3
420.2 go: downloading go.jolheiser.com/hcaptcha v0.0.4
421.4 Running go generate...
421.5 go: downloading go.jolheiser.com/pwn v0.0.3
421.5 go: downloading go.jolheiser.com/hcaptcha v0.0.4
421.5 go: downloading github.com/mattn/go-sqlite3 v1.14.15
423.0 go: downloading github.com/lunny/vfsgen v0.0.0-20220105142115-2c99e1ffdfa0
423.0 go: downloading github.com/shurcooL/httpfs v0.0.0-20190707220628-8d4bc4ba7749
423.2 generating bindata for migration
423.3 generating bindata for options
423.8 generating bindata for public
425.2 generating bindata for templates
425.9 CGO_CFLAGS="-g -O2 -DSQLITE_MAX_VARIABLE_NUMBER=32766" go build -v -tags 'bindata timetzdata sqlite sqlite_unlock_notify' -ldflags '-s -w -X "main.MakeVersion=GNU Make 4.3" -X "main.Version=1.18.5" -X "main.Tags=bindata timetzdata sqlite sqlite_unlock_notify"' -o gitea
425.9 go: downloading go.jolheiser.com/pwn v0.0.3
425.9 go: downloading go.jolheiser.com/hcaptcha v0.0.4
426.1 get "go.jolheiser.com/hcaptcha": found meta tag vcs.metaImport{Prefix:"go.jolheiser.com/hcaptcha", VCS:"git", RepoRoot:"https://git.jojodev.com/jolheiser/hcaptcha.git"} at //go.jolheiser.com/hcaptcha?go-get=1
426.1 get "go.jolheiser.com/pwn": found meta tag vcs.metaImport{Prefix:"go.jolheiser.com/pwn", VCS:"git", RepoRoot:"https://git.jojodev.com/jolheiser/pwn.git"} at //go.jolheiser.com/pwn?go-get=1
428.6 modules/hcaptcha/hcaptcha.go:12:2: reading go.jolheiser.com/hcaptcha/go.mod at revision v0.0.4: git ls-remote -q origin in /go/pkg/mod/cache/vcs/ef3d79b39382e527acfd165be9b783d048675767dd531fc8f9a1d98b0456091c: exit status 128:
428.6 fatal: could not read Username for 'https://git.jojodev.com': terminal prompts disabled
428.6 Confirm the import path was entered correctly.
428.6 If this is a private repository, see https://golang.org/doc/faq#git_https for additional information.
428.6 modules/auth/password/pwn.go:12:2: reading go.jolheiser.com/pwn/go.mod at revision v0.0.3: git ls-remote -q origin in /go/pkg/mod/cache/vcs/786a97460bd4f3de914d0fc0218c25c3cf69c8ace8bb4b23e40bdf769bf2e325: exit status 128:
428.6 fatal: could not read Username for 'https://git.jojodev.com': terminal prompts disabled
428.6 Confirm the import path was entered correctly.
428.6 If this is a private repository, see https://golang.org/doc/faq#git_https for additional information.
428.6 make: *** [Makefile:733: gitea] Error 1

Now, looking at these modules here, they report their repositories correctly:

Apologies, but my 'go' familiarity is limited, so, look as I may, I could not find a work around for this, where the correct repository location could be properly set to "override" what is being reported.

How can I get beyond this to properly build a v1.18.5 image?

Gitea Version

1.18.5

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.45.2

Operating System

MacOS Sonoma 14.5

How are you running Gitea?

We utilize gitea in K8s.

Database

PostgreSQL

Originally created by @zcopado on GitHub (Jul 1, 2024). ### Description Upon attempting to build the docker image for gitea v1.18.5, it fails as follows: > 420.2 go: downloading go.jolheiser.com/pwn v0.0.3 > 420.2 go: downloading go.jolheiser.com/hcaptcha v0.0.4 > 421.4 Running go generate... > 421.5 go: downloading go.jolheiser.com/pwn v0.0.3 > 421.5 go: downloading go.jolheiser.com/hcaptcha v0.0.4 > 421.5 go: downloading github.com/mattn/go-sqlite3 v1.14.15 > 423.0 go: downloading github.com/lunny/vfsgen v0.0.0-20220105142115-2c99e1ffdfa0 > 423.0 go: downloading github.com/shurcooL/httpfs v0.0.0-20190707220628-8d4bc4ba7749 > 423.2 generating bindata for migration > 423.3 generating bindata for options > 423.8 generating bindata for public > 425.2 generating bindata for templates > 425.9 CGO_CFLAGS="-g -O2 -DSQLITE_MAX_VARIABLE_NUMBER=32766" go build -v -tags 'bindata timetzdata sqlite sqlite_unlock_notify' -ldflags '-s -w -X "main.MakeVersion=GNU Make 4.3" -X "main.Version=1.18.5" -X "main.Tags=bindata timetzdata sqlite sqlite_unlock_notify"' -o gitea > 425.9 go: downloading go.jolheiser.com/pwn v0.0.3 > 425.9 go: downloading go.jolheiser.com/hcaptcha v0.0.4 > 426.1 get "go.jolheiser.com/hcaptcha": found meta tag vcs.metaImport{Prefix:"go.jolheiser.com/hcaptcha", VCS:"git", RepoRoot:"https://git.jojodev.com/jolheiser/hcaptcha.git"} at //go.jolheiser.com/hcaptcha?go-get=1 > 426.1 get "go.jolheiser.com/pwn": found meta tag vcs.metaImport{Prefix:"go.jolheiser.com/pwn", VCS:"git", RepoRoot:"https://git.jojodev.com/jolheiser/pwn.git"} at //go.jolheiser.com/pwn?go-get=1 > 428.6 modules/hcaptcha/hcaptcha.go:12:2: reading go.jolheiser.com/hcaptcha/go.mod at revision v0.0.4: git ls-remote -q origin in /go/pkg/mod/cache/vcs/ef3d79b39382e527acfd165be9b783d048675767dd531fc8f9a1d98b0456091c: exit status 128: > 428.6 fatal: could not read Username for 'https://git.jojodev.com': terminal prompts disabled > 428.6 Confirm the import path was entered correctly. > 428.6 If this is a private repository, see https://golang.org/doc/faq#git_https for additional information. > 428.6 modules/auth/password/pwn.go:12:2: reading go.jolheiser.com/pwn/go.mod at revision v0.0.3: git ls-remote -q origin in /go/pkg/mod/cache/vcs/786a97460bd4f3de914d0fc0218c25c3cf69c8ace8bb4b23e40bdf769bf2e325: exit status 128: > 428.6 fatal: could not read Username for 'https://git.jojodev.com': terminal prompts disabled > 428.6 Confirm the import path was entered correctly. > 428.6 If this is a private repository, see https://golang.org/doc/faq#git_https for additional information. > 428.6 make: *** [Makefile:733: gitea] Error 1 Now, looking at these modules here, they report their repositories correctly: - https://pkg.go.dev/go.jolheiser.com/pwn --> https://gitea.com/jolheiser/pwn.git - https://pkg.go.dev/go.jolheiser.com/hcaptcha --> https://gitea.com/jolheiser/hcaptcha.git Apologies, but my 'go' familiarity is limited, so, look as I may, I could not find a work around for this, where the correct repository location could be properly set to "override" what is being reported. How can I get beyond this to properly build a v1.18.5 image? ### Gitea Version 1.18.5 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.45.2 ### Operating System MacOS Sonoma 14.5 ### How are you running Gitea? We utilize gitea in K8s. ### Database PostgreSQL
GiteaMirror added the type/bug label 2025-11-02 10:35:23 -06:00
GiteaMirror commented 2025-11-02 10:35:24 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Jul 1, 2024):

Generally the go proxy should have accounted for this, I haven't hosted those modules since I moved them into the repo directly.
I'll add a proper redirect for them in a moment, which should fix the issue.

EDIT: I should also clarify I suggest using a newer version! But in the event something is keeping you back I can deploy a fix, and regardless I want to be a good steward of my Go modules.

@jolheiser commented on GitHub (Jul 1, 2024): Generally the go proxy should have accounted for this, I haven't hosted those modules since I moved them into the repo directly. I'll add a proper redirect for them in a moment, which should fix the issue. EDIT: I should also clarify I suggest using a newer version! But in the event something is keeping you back I can deploy a fix, and regardless I want to be a good steward of my Go modules.
GiteaMirror commented 2025-11-02 10:35:24 -06:00
Author
Owner
Copy Link

@zcopado commented on GitHub (Jul 1, 2024):

Thank you @jolheiser. The last time we built this image was July 2023, and this was not a problem then.

Cheers, and thank you for the prompt response.

@zcopado commented on GitHub (Jul 1, 2024): Thank you @jolheiser. The last time we built this image was July 2023, and this was not a problem then. Cheers, and thank you for the prompt response.
GiteaMirror commented 2025-11-02 10:35:25 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jul 1, 2024):

Hi @zcopado it is strongly recommended that you use the current stable version of Gitea as it has bug fixes and security patches that aren't included in 1.18.X
Can I ask why you are using the EOL-version instead of something more recent?

@techknowlogick commented on GitHub (Jul 1, 2024): Hi @zcopado it is strongly recommended that you use the current stable version of Gitea as it has bug fixes and security patches that aren't included in 1.18.X Can I ask why you are using the EOL-version instead of something more recent?
GiteaMirror commented 2025-11-02 10:35:25 -06:00
Author
Owner
Copy Link

@zcopado commented on GitHub (Jul 1, 2024):

@techknowlogick - of course. We utilize gitea as a basis for an internal service offering. We customize templates, etc, and every time we upgrade, we have to go through the process of adapting the templates, etc.

We are currently planning a jump to gitea 1.20.x within the next 30 - 60 days, but we only update 1-2x annually.

Our current stable version is on v1.18.5. Hope that helps clarify.

@zcopado commented on GitHub (Jul 1, 2024): @techknowlogick - of course. We utilize gitea as a basis for an internal service offering. We customize templates, etc, and every time we upgrade, we have to go through the process of adapting the templates, etc. We are currently planning a jump to gitea 1.20.x within the next 30 - 60 days, but we only update 1-2x annually. Our current stable version is on v1.18.5. Hope that helps clarify.
GiteaMirror commented 2025-11-02 10:35:25 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Jul 1, 2024):

I've updated my webserver for those two modules. Good luck with your update! 🙂

@jolheiser commented on GitHub (Jul 1, 2024): I've updated my webserver for those two modules. Good luck with your update! 🙂
GiteaMirror commented 2025-11-02 10:35:25 -06:00
Author
Owner
Copy Link

@zcopado commented on GitHub (Jul 1, 2024):

@jolheiser - Worked like a charm. Cheers.

@zcopado commented on GitHub (Jul 1, 2024): @jolheiser - Worked like a charm. Cheers.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#13222
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?