Bug 213679 - www/py-django16-tastypie: Should deprecate because django16 expired
Summary: www/py-django16-tastypie: Should deprecate because django16 expired
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Dan Langille
URL:
Keywords: needs-patch
Depends on:
Blocks: 213269
  Show dependency treegraph
 
Reported: 2016-10-21 15:13 UTC by VK
Modified: 2017-04-19 19:47 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description VK freebsd_triage 2016-10-21 15:13:19 UTC
www/django16 expired on 2015-10-01, so this port should expire as well. This port is a slave of py-django-tastypie which depends on www/django18, so I guess it can be retired.
Comment 1 William Grzybowski freebsd_committer freebsd_triage 2016-10-21 15:16:09 UTC
Are you a committer? Feel free to remove it if so.
I wont have time anytime soon.
Comment 2 VK freebsd_triage 2016-10-21 15:19:21 UTC
Oops, there must be a bug here, www/py-django16-tastypie is maintained by dvl@. Freshports is showing wrong, and Bugzilla assigned wrong.

Reassign and CC wg@ who maintains www/py-django-tastypie.
Comment 3 VK freebsd_triage 2016-10-21 15:20:17 UTC
(In reply to William Grzybowski from comment #1)

No, just a triager. But I can submit a patch for anyone to take.
Comment 4 Dan Langille freebsd_committer freebsd_triage 2016-10-21 23:40:28 UTC
(In reply to Vladimir Krstulja from comment #2)

MAINTAINER is set in the Makefile: MAINTAINER= dvl@FreeBSD.org

But this port has masterport: MASTERDIR=  ${.CURDIR}/../py-django-tastypie

This reports the maintainer of the masterport:

$ make -V MAINTAINER
wg@FreeBSD.org
Comment 5 Dan Langille freebsd_committer freebsd_triage 2016-10-22 00:06:14 UTC
Any consensus on whether I should do an svn cp or an svn mv on www/py-django16-tastypie to www/py-django18-tastypie

I will also do the same to devel/py-django16-tastypie-mongoengine which depends upon www/py-django16-tastypie
Comment 6 commit-hook freebsd_committer freebsd_triage 2016-10-22 08:22:23 UTC
A commit references this bug:

Author: koobs
Date: Sat Oct 22 08:21:52 UTC 2016
New revision: 424452
URL: https://svnweb.freebsd.org/changeset/ports/424452

Log:
  www/py-django-tastypie: Allow MAINTAINER override

  Allow MAINTAINER to be overridden as there is a sub-port
  (www/py-django16-tastypie) maintained by someone else (dvl).

  This fixes Bugzilla AutoAssigner incorrectly assignments
  and incorrect display of MAINTAINER in freshports.org

  PR:		213679
  Reported by:	Vladimir Krstulja <vlad-fbsd acheronmedia com>>

Changes:
  head/www/py-django-tastypie/Makefile
Comment 7 Kubilay Kocak freebsd_committer freebsd_triage 2016-10-22 08:27:28 UTC
(In reply to Dan Langille from comment #4)

I wouldn't use move for renames including version updates (foo16 -> foo18).

Having said that, I'm sure someone might argue both a move and copy/delete require a MOVED entry and a single operation is better than one.

Having said that, as a user of a port fooXY, I would *not* expect that port ever to move past version X.Y, which a move would do.

My vote would be for a copy+version update (new port), and then a deletion of 16 (expired), OR, just delete django16-*, and create a new django18-* (without the history).
Comment 8 Antoine Brodin freebsd_committer freebsd_triage 2016-10-23 09:13:40 UTC
(In reply to Dan Langille from comment #5)
devel/py-django-tastypie-mongoengine and www/py-django-tastypie already exist in the ports tree and use django 1.8,  so adding duplicates doesn't seem necessary.
Comment 9 VK freebsd_triage 2016-11-13 18:29:16 UTC
Sooo.... can we deprecate/remove this port then? :)
Comment 10 Dan Langille freebsd_committer freebsd_triage 2016-11-13 22:11:15 UTC
security/py-crits requires 1.6 but I'll check on Monday if we're still interested in that port.
Comment 11 VK freebsd_triage 2016-11-26 16:42:13 UTC
Any news?
Comment 12 Dan Langille freebsd_committer freebsd_triage 2016-11-26 17:26:26 UTC
Sorry, no, work was crazy this past week.
Comment 13 Martin Wilke freebsd_committer freebsd_triage 2017-03-03 07:40:31 UTC
ping?
Comment 14 Dan Langille freebsd_committer freebsd_triage 2017-03-04 16:24:15 UTC
No change in my situation.  If anyone wishes to proceed without me, please do so. This weekend I have to concentrate on conferences.  My apologies.
Comment 15 Rene Ladan freebsd_committer freebsd_triage 2017-04-19 19:47:21 UTC
Expired port removed.