[Bug 255307] net/py-pynsq: update to 0.9.0 (fixes indirect conflict with math/py-matplotlib)

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 255307
           Summary: net/py-pynsq: update to 0.9.0 (fixes indirect conflict
                    with math/py-matplotlib)
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: koobs at FreeBSD.org
          Reporter: jcfyecrayz at liamekaens.com
          Assignee: koobs at FreeBSD.org
             Flags: maintainer-feedback?(koobs at FreeBSD.org)

Created attachment 224333
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=224333&action=edit
[patch] update to 0.9.0

Update py-pynsq to 0.9.0

0.9.0 now supports tornado > 5

 This is important for playing well in the ports tree.  It avoids
 the problem of, for example, py-matplotlib depending on www/py-tornado
 (currently 6.1) and py-pynsq depending on www/py-tornado5 (5.1.1).
 These two tornado versions currently install conflicting files,
 so this effectively prevents users from installing py-pynsq when
 py-matplotlib is installed.  There may be other similar examples
 of dependency issues.

 tornado6 & tornado5 might be able to co-exist, but I suspect that
 would be a lot harder to implement (probably requiring leaf port
 changes).


0.9.0 also addresses some other issues:
https://github.com/nsqio/pynsq/releases/tag/v0.9.0

In addition to the tornado support update, the most notable changes
are IPv6 support and improved RDY handling.



Note regarding PORTVERSION / DISTVERSION:

When this port was updated to 0.9.0b1, it should have used DISTVERSION
instead of PORTVERSION.

This would have generated a PORTVERSION of 0.9.0.b1.  It seems
upstream intended b1 to mean beta #1 (rather than a "later" minor
update to 0.9.0).  0.9.0.b1 is better for package versioning
comparison.

Now that we want to update to 0.9.0, version comparison thinks
0.9.0b1 is later than 0.9.0

Address this by using DISTVERSION=0.9.0 so the fetch gets the
right version - and because 0.9.0<0.9.0b1, set PORTVERSION=0.9.0rel
which evaluates to later than 0.9.0b1.  This is better than using
a permanent PORTEPOCH bump.

% pkg version --test-version 0.9.0 0.9.0b1_1
<
% pkg version --test-version 0.9.0 0.9.0.b1_1
>
% pkg version --test-version 0.9.0rel 0.9.0b1_1
>

The porter's handbook currently documents this situation fairly well.
See section 5.2.2, particularly example 5.4 and 5.5.

I appreciate the subtle distinction between DISTVERSION & PORTVERSION
(pre-release designators such as alpha, beta, etc. vs. post-release patch
levels) a wee bit more after dealing with this particular case.  I'll think
twice before just updating PORTVERSION for a port update in the future since
every upstream will apply versioning per its own (sometimes not well thought
out) scheme.

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