[Bug 193425] New: [MAINTAINER] science/jstrack: Fix BROKEN

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193425

            Bug ID: 193425
           Summary: [MAINTAINER] science/jstrack: Fix BROKEN
           Product: Ports Tree
           Version: Latest
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: 5u623l20 at gmail.com
 Attachment #147002 maintainer_approval+
             Flags:

Created attachment 147002
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147002&action=edit
patch for jstrack-3.3.4

- Fix BROKEN

Upstream changed the distfiles without bumping port version for removing some
old data from the distfiles. 

Snippet from my mail with the author:
> Did you recently change the distfile without bumping version number? I
> will fix it but prior to that I need to know the proper reason.

Yes.  I don't remember exactly what it was, but it was a simple issue
with the archive file itself.  So I fixed that.  I definitely know
there were no changes to JStrack---I always change the version number
if I add a patch or add new features.

As for the "proper reason", if I see a need to patch something in the
distribution, say, add storm data that I'd forgotten to add previously,
move storm data from storms to storms/old/YEAR/..., etc., I do it.  I
don't change the version number unless there's a change to JStrack's
code (which obviously includes the filters for NHC data).  If it's
2014, and I see that there is 2013 code in the storms directory in the
dist file, I fix that.  And so on.....  Those are more than enough of
a "proper reason" for me.  :-)

Poudriere logs:
http://pdr.s.ubze.ro/bulk/latest-per-pkg/jstrack/3.3.4/

-- 
You are receiving this mail because:
You are the assignee for the bug.