Alexey, I tried the usual gomod vendor stuff, and found these 404 # Errors found during processing: # tuple.discoverMirrors https://storj.io/drpc?go-get=1: status 404 # tuple.discoverMirrors https://storj.io/common?go-get=1: status 404 # tuple.discoverMirrors https://storj.io/monkit-jaeger?go-get=1: status 404 # tuple.discoverMirrors https://storj.io/private?go-get=1: status 404 # tuple.discoverMirrors https://storj.io/uplink?go-get=1: status 404 Did you run into these before, or is this a breakage in modules2tuple?
A commit references this bug: Author: danfe Date: Mon Mar 15 05:50:10 UTC 2021 New revision: 568430 URL: https://svnweb.freebsd.org/changeset/ports/568430 Log: Update to version 1.24.4. PR: 254219 Changes: head/net/storj/Makefile head/net/storj/Makefile.deps head/net/storj/distinfo
(In reply to Dave Cottlehuber from comment #1) > Did you run into these before, or is this a breakage in modules2tuple? My version of modules2tuple works (it's an older patched version, don't see a reason to upgrade), but the port itself did not build for me on the day of the release. It builds now though, so I've updated the port with ports r568430, thanks for the headsup.
P.S. Gian-Simon, while we appreciate any input from our users, it is generally expected to find some sensible material about the issue at hand, like a patch, or an excerpt from the failing build log, or detailed explanation of a particular problem. Just pointing out that the new version had been released does not really warrant opening a PR, emailing maintainer is usually enough in this case. If it's an unmaintained port, consider adopting it! (and that's a valid PR reason :-)
Hy Alexey, Thanks for updating the port, i had not much luck with writing Emails in the past. I provided some patches, but even when the port had a maintainer (not a @freebsd.org one) it sat open for weeks (often more then 3). But anyway thanks for updating.