Bug 280334 - sysutils/helmfile: update to 0.167.0
Summary: sysutils/helmfile: update to 0.167.0
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Vladimir Druzenko
URL: https://github.com/helmfile/helmfile/...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-17 16:00 UTC by Pavel Timofeev
Modified: 2024-07-31 19:27 UTC (History)
1 user (show)

See Also:


Attachments
port patch (1.93 KB, patch)
2024-07-17 16:00 UTC, Pavel Timofeev
timp87: maintainer-approval+
Details | Diff
port patch 2 (1.94 KB, patch)
2024-07-31 18:00 UTC, Pavel Timofeev
timp87: maintainer-approval+
Details | Diff
port patch 0.167.0 (1.93 KB, patch)
2024-07-31 18:08 UTC, Pavel Timofeev
timp87: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Timofeev 2024-07-17 16:00:09 UTC
Created attachment 252128 [details]
port patch

sysutils/helmfile: update to 0.166.0
Comment 1 Vladimir Druzenko freebsd_committer freebsd_triage 2024-07-17 16:51:44 UTC
fetch: https://proxy.golang.org/github.com/helmfile/helmfile/@v/v0.166.0.mod: size mismatch: expected 15162, actual 15182

I'll recreate distinfo.
Comment 2 Vladimir Druzenko freebsd_committer freebsd_triage 2024-07-17 18:50:03 UTC
"make makesum" download v0.166.0.mod with size 15162, but "make fetch" - "15182".
I already hear about this before, but can't remember how to fix this…
Comment 3 Vladimir Druzenko freebsd_committer freebsd_triage 2024-07-17 19:22:50 UTC
$ diff -u /usr/ports/distfiles/go/sysutils_helmfile/helmfile-v0.166.0/v0.166.0.mod v0.166.0.mod
--- /usr/ports/distfiles/go/sysutils_helmfile/helmfile-v0.166.0/v0.166.0.mod
+++ v0.166.0.mod
@@ -2,6 +2,8 @@

 go 1.22.4

+toolchain go1.22.2
+
 require (
        github.com/Masterminds/semver/v3 v3.2.1
        github.com/Masterminds/sprig/v3 v3.2.3
Comment 4 Vladimir Druzenko freebsd_committer freebsd_triage 2024-07-25 19:07:04 UTC
ping
Comment 5 Pavel Timofeev 2024-07-25 19:11:13 UTC
Sorry, do you know how to deal with this properly?
Comment 6 Vladimir Druzenko freebsd_committer freebsd_triage 2024-07-25 19:13:04 UTC
(In reply to Pavel Timofeev from comment #5)
If I knew, I would have already suggested how to fix it...
Comment 7 Pavel Timofeev 2024-07-25 19:16:50 UTC
Let me try to ask upstream what is going on
Comment 8 Pavel Timofeev 2024-07-31 18:00:49 UTC
Created attachment 252404 [details]
port patch 2

Update to 0.167.0
Comment 9 Pavel Timofeev 2024-07-31 18:03:40 UTC
Wait a second. I will regenerate patch. I did it under unusual git user.
Comment 10 Pavel Timofeev 2024-07-31 18:08:48 UTC
Created attachment 252405 [details]
port patch 0.167.0
Comment 11 Pavel Timofeev 2024-07-31 18:09:15 UTC
Done
Can you try this one?
Comment 12 Vladimir Druzenko freebsd_committer freebsd_triage 2024-07-31 19:00:32 UTC
(In reply to Pavel Timofeev from comment #11)
Fetched correct now!
I'll commit it soon.
Comment 14 Vladimir Druzenko freebsd_committer freebsd_triage 2024-07-31 19:09:14 UTC
What was it?
Comment 15 Pavel Timofeev 2024-07-31 19:27:17 UTC
(In reply to Vladimir Druzenko from comment #14)
To be honest I have no idea. They just released a new version with proper file before I even was able to properly report the issue.