Created attachment 253514 [details] [PATCH] net/krakend-ce: update 2.7.0 → 2.7.1
Build fails on armv7 FreeBSD 14: # github.com/krakendio/krakend-amqp/v2 vendor/github.com/krakendio/krakend-amqp/v2/consumer.go:47:20: cannot use math.MaxInt64 (untyped int constant 9223372036854775807) as int value in assignment (overflows) vendor/github.com/krakendio/krakend-amqp/v2/producer.go:64:20: cannot use math.MaxInt64 (untyped int constant 9223372036854775807) as int value in assignment (overflows) golang.org/x/sync/errgroup github.com/hashicorp/golang-lru/simplelru github.com/luraproject/lura/v2/async # github.com/luraproject/lura/v2/async vendor/github.com/luraproject/lura/v2/async/asyncagent.go:85:34: cannot use math.MaxInt64 (untyped int constant 9223372036854775807) as int value in assignment (overflows) Please check. Shall I hold the update or would you like to proceed and fix this later?
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=d313252e4dda12b481a4d0fba69bd62d651344b1 commit d313252e4dda12b481a4d0fba69bd62d651344b1 Author: Älven <alster@vinterdalen.se> AuthorDate: 2024-09-22 10:27:46 +0000 Commit: Robert Clausecker <fuz@FreeBSD.org> CommitDate: 2024-09-25 06:29:01 +0000 net/krakend-ce: update to 2.7.1 - broken on armv7 Changelog: https://github.com/krakend/krakend-ce/releases PR: 281455 Event: EuroBSDcon 2024 net/krakend-ce/Makefile | 3 ++- net/krakend-ce/distinfo | 10 +++++----- net/krakend-ce/pkg-descr | 10 +++++----- 3 files changed, 12 insertions(+), 11 deletions(-)
Thank you for your contribution.
Thank you! Exactly what I would vote for. P.S. May I even add armv7 to NOT_FOR_ARCHS, just as i386 and likely for the same reason?
(In reply to Älven from comment #4) NOT_FOR_ARCHS is for architectures for which the code is not designed and will never work. BROKEN is for architectures for which the code is broken, but could be fixed. Which of the two is it?
Thank you for the explanation. (In reply to Robert Clausecker from comment #5) > Which of the two is it? Don't know for sure. Likely you were right, so I won't not to change it.