Bug 243028 - www/py-puppetboard: unify ports and update to a recent release
Summary: www/py-puppetboard: unify ports and update to a recent release
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Allan Jude
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-01 23:15 UTC by Romain Tartière
Modified: 2020-01-03 19:50 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (allanjude)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Romain Tartière freebsd_committer freebsd_triage 2020-01-01 23:15:51 UTC 
Hi Allan,

We currently have 3 ports for PuppetBoard:
- www/py-puppetboard   v0.0.4
- www/py-puppetboard02 v0.2.2 (deprecated)
- www/py-puppetboard03 v0.3.0

These ports depends on Python 2.7 which has reached EOL.  The project has been fixed upstream to works with Python 3 and was released as 1.0.0, so I guess it's time to tidy the FreeBSD ports and prune the pre-release versions.

I propose to update www/py-puppetboard to install the latest version of PuppetBoard (1.1.0 as of today) and remove the other ports.

Same for databases/py-pypuppetdb and databases/py-pypuppetdb03: only provide a single port (databases/py-pypuppetdb) with the latest version of the software (1.2.0 as of today).


We have these different ports because you where locked with old versions of PuppetDB.  has the situation evolved?  If so, does this look acceptable?  Would you like puppet@ to take maintainership of this?

Thanks!
Comment 1 Allan Jude freebsd_committer freebsd_triage 2020-01-03 00:44:27 UTC 
Hi Romain,

Thanks for reaching out. Yes, in the past we were stuck to older versions of PuppetDB and thus required older versions of py-puppetboard, because they did not work with newer PuppetDB.

Thanks to your work to get the latest PuppetServer working on FreeBSD 12, we are not stuck in a similar situation anymore.

I am fine with removing all of the old ports, and yes, if puppet@ would be willing to take over maintainership, that should be great.
Comment 2 commit-hook freebsd_committer freebsd_triage 2020-01-03 19:40:58 UTC 
A commit references this bug:

Author: romain
Date: Fri Jan  3 19:40:00 UTC 2020
New revision: 521954
URL: https://svnweb.freebsd.org/changeset/ports/521954

Log:
  Unify and update databases/py-pypuppetdb to 1.2.0

  PR:		243028
  Reported by:	romain
  Approved by:	allanjude
  With hat:	puppet

Changes:
  head/databases/py-pypuppetdb/Makefile
  head/databases/py-pypuppetdb/distinfo
  head/databases/py-pypuppetdb03/Makefile
Comment 3 commit-hook freebsd_committer freebsd_triage 2020-01-03 19:48:59 UTC 
A commit references this bug:

Author: romain
Date: Fri Jan  3 19:47:57 UTC 2020
New revision: 521955
URL: https://svnweb.freebsd.org/changeset/ports/521955

Log:
  Unify and update www/py-puppetboard to 1.1.0

  PR:		243028
  Reported by:	romain
  Approved by:	allanjude
  With hat:	puppet

Changes:
  head/www/py-puppetboard/Makefile
  head/www/py-puppetboard/distinfo
  head/www/py-puppetboard/files/
  head/www/py-puppetboard02/Makefile
  head/www/py-puppetboard03/Makefile
Comment 4 Romain Tartière freebsd_committer freebsd_triage 2020-01-03 19:50:15 UTC 
Committed, thanks!