Date: Sun, 17 Mar 2013 06:18:56 GMT From: Danny Warren <danny@dannywarren.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/177045: mail/dspam: Bring dspam up to date with latest stable upstream release Message-ID: <201303170618.r2H6Iudg036014@red.freebsd.org> Resent-Message-ID: <201303170620.r2H6K06o030129@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 177045 >Category: ports >Synopsis: mail/dspam: Bring dspam up to date with latest stable upstream release >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Sun Mar 17 06:20:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Danny Warren >Release: 9.1-RELEASE >Organization: >Environment: 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: The latest upstream release of dspam is 3.10.2, which was released almost a year ago in April of 2012. The mail/dspam port is stuck at version 3.9.0, which is over three years old. The mail/dspam-devel port is also a version behind (see PR #167289). It looks like back in 2011, we stopped merging over changes from dspam-devel to the main dspam port once they became stable, as was the process in the past. I'm unclear why that happened, as I can't find any explanation in svn comments or in any problem reports. It doesn't seem to be a backwards compatibility or painful upgrade issue either, as the release notes for dspam itself states: "We expect no changes are required to upgrade to 3.10.0" So basically, dspam-devel has become the de-facto stable port. Which probably shouldn't be the case. Thoughts? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201303170618.r2H6Iudg036014>