Bug 254219

Summary: [net/storj]: Update to 1.24.4
Product: Ports & Packages Reporter: Gian-Simon Purkert <gspurki>
Component: Individual Port(s)Assignee: Alexey Dokuchaev <danfe>
Status: Closed FIXED    
Severity: Affects Only Me CC: dch
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   

Description Gian-Simon Purkert 2021-03-11 16:28:19 UTC

    
Comment 1 Dave Cottlehuber freebsd_committer freebsd_triage 2021-03-13 09:17:02 UTC
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?
Comment 2 commit-hook freebsd_committer freebsd_triage 2021-03-15 05:50:32 UTC
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
Comment 3 Alexey Dokuchaev freebsd_committer freebsd_triage 2021-03-15 05:54:53 UTC
(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.
Comment 4 Alexey Dokuchaev freebsd_committer freebsd_triage 2021-03-15 06:03:26 UTC
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 :-)
Comment 5 Gian-Simon Purkert 2021-03-15 11:53:17 UTC
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.