Created attachment 166422 [details] patch with expiration setting Hello, attached patch set expiration date for both ports. These ports has reached their EOL and are not supported anymore: http://www.pgpool.net/pipermail/pgpool-general/2016-February/004443.html Greetings, Torsten
Thanks Torsten, could you update the patch to say: please update to category/port instead of : current version This will ensure that the user is provided the information that need at the time the message is presented to install something else, rather than go looking elsewhere.
Correctly assign to MAINTAINER, please use "category/port" format for *all* relevant ports in the Summary
(In reply to Kubilay Kocak from comment #1) > Thanks Torsten, could you update the patch to say: > please update to category/port That is a surprisingly hard request. :D We have: pgpool pgpool-II pgpool-II-22 pgpool-II-23 pgpool-II-30 pgpool-II-33 pgpool-II contains 3.1.x and pgpool 3.4.x First: the most current version is 3.5. and it is not in the ports. I would mostly refer to databases/pgpool but the port is wrongly named. The correct name would be databases/pgpool-II which points to an even older version. And nearly every port is not up to date... After some more thoughts about this confusion, i would propose the following solution: 1. rename databases/pgpool-II to databases/pgpool-II-31 2. rename databases/pgpool to databases/pgpool-II-34 3. create databases/pgpool-II with current 3.5 version 4. expire 2.2 and 2.3 and point user to new databases/pgpool-II 5. update all the ports left What is your opinion? Greetings, Torsten
For the archive: pgpool 3.0 (port: databases/pgpool-II-30) reached its EOL today and is no longer supported or maintained.
I have no patches but I, too, realized that all the pgpool-ports in the ports-tree are basically worthless at this point - and most could be expired right now (though that's probably "illegal"). I think, if you have patches that add the new ports as per your suggestion, it would be best to submit them in new tickets and have the ports added an expiry date.
A commit references this bug: Author: tz Date: Thu Mar 2 12:24:34 UTC 2017 New revision: 435231 URL: https://svnweb.freebsd.org/changeset/ports/435231 Log: databases/pgpool: Update from 3.4.3 to 3.4.9 Changelog: http://www.pgpool.net/docs/pgpool-II-3.4.8/NEWS.txt Changelog: http://www.pgpool.net/docs/latest/en/html/release-3-4-9.html PR: 206839 Submitted by: Felix Hanley <felix@userspace.com.au> Changes: head/databases/pgpool/Makefile head/databases/pgpool/distinfo
A commit references this bug: Author: tz Date: Tue Mar 14 15:51:13 UTC 2017 New revision: 436162 URL: https://svnweb.freebsd.org/changeset/ports/436162 Log: Deprecate databases/pgpool-II-22 and databases/pgpool-II-23 They are deprecated by upstream for a long time PR: 206839 Changes: head/databases/pgpool-II-22/Makefile head/databases/pgpool-II-23/Makefile
I deleted databases/pgool-II-22 and databases/pgpool-II-23 today in r438507
A commit references this bug: Author: tz Date: Mon May 15 13:40:51 UTC 2017 New revision: 440924 URL: https://svnweb.freebsd.org/changeset/ports/440924 Log: databases/pgpool-II: set DEPRECATED pgpool 3.1.x was deprecated by upstream in September 2016 PR: 206839 Approved by: maintainer (timeout) Changes: head/databases/pgpool-II/Makefile
A commit references this bug: Author: tz Date: Mon May 15 13:44:32 UTC 2017 New revision: 440925 URL: https://svnweb.freebsd.org/changeset/ports/440925 Log: databases/pgpool-II-30: set DEPRECATED and EXPIRATION_DATE pgpool 3.0.x is EOL since 2016-02-05 PR: 206839 Approved by: maintainer (timeout) Changes: head/databases/pgpool-II-30/Makefile
A commit references this bug: Author: tz Date: Mon May 15 13:48:18 UTC 2017 New revision: 440927 URL: https://svnweb.freebsd.org/changeset/ports/440927 Log: databases/pgpool: Update from 3.4.9 to 3.4.11 Changelog: http://www.pgpool.net/docs/latest/en/html/release-3-4-10.html Changelog: http://www.pgpool.net/docs/latest/en/html/release-3-4-11.html PR: 206839 Changes: head/databases/pgpool/Makefile head/databases/pgpool/distinfo
Expiring two more ports which reach EOL last year and updated 3.4.x to newest release. I think we should just let the wrongly named ports expire. Maybe i will rename 3.4, since it will stay there for 2 more years. But the rest will clean up relatively fast. :) Now we just misses the new 3.5 and 3.6 in ports-tree.
A commit references this bug: Author: tz Date: Tue May 16 08:58:32 UTC 2017 New revision: 440992 URL: https://svnweb.freebsd.org/changeset/ports/440992 Log: databases/pgpool: Limit PORTSCOUT to 3.4.x Future pgpool version of 3.5 and 3.6 will get an own port, therefore limiting the PORTSCOUT check to actual branch PR: 206839 Changes: head/databases/pgpool/Makefile
A commit references this bug: Author: tz Date: Tue May 16 10:19:07 UTC 2017 New revision: 440994 URL: https://svnweb.freebsd.org/changeset/ports/440994 Log: New port: databases/pgpool-II-35 This is an repo-copy of databases/pgpool updated to 3.5.8 PR: 206839 Changes: head/databases/Makefile head/databases/pgpool-II-35/ head/databases/pgpool-II-35/Makefile head/databases/pgpool-II-35/distinfo head/databases/pgpool-II-35/pkg-plist
A commit references this bug: Author: tz Date: Tue May 16 10:57:50 UTC 2017 New revision: 440995 URL: https://svnweb.freebsd.org/changeset/ports/440995 Log: New port: databases/pgpool-II-36 This is an repo-copy of databases/pgpool-II-35 updated to 3.6.4 PR: 206839 Changes: head/databases/Makefile head/databases/pgpool-II-36/ head/databases/pgpool-II-36/Makefile head/databases/pgpool-II-36/distinfo head/databases/pgpool-II-36/pkg-plist
All outdated pgpool-versions are marked. The new version 3.5 and 3.6 are now in the ports. It took some time - but now: lets close the PR.