From owner-freebsd-python@freebsd.org Wed Apr 18 10:09:04 2018 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63F1DFA56C2 for ; Wed, 18 Apr 2018 10:09:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 81CB881EA1 for ; Wed, 18 Apr 2018 10:09:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id E549AFA56BD; Wed, 18 Apr 2018 10:09:02 +0000 (UTC) Delivered-To: python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0DA7FA56BC for ; Wed, 18 Apr 2018 10:09:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0678A81E55 for ; Wed, 18 Apr 2018 10:09:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 444185E17 for ; Wed, 18 Apr 2018 10:09:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3IA90Wh023936 for ; Wed, 18 Apr 2018 10:09:00 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3IA90UV023935 for python@FreeBSD.org; Wed, 18 Apr 2018 10:09:00 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 227416] [NEW PORT] net-mgmt/netbox: IPAM and DCIM management tool Date: Wed, 18 Apr 2018 10:09:01 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd_ports@k-worx.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: pi@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2018 10:09:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227416 --- Comment #13 from Kai --- (In reply to Kurt Jaeger from comment #12) Thank you very much for the testbuilds, I'm positively surprised because I = have not expected that this PR would come so far in such a short time and there'= s no hurry. A bit work is still needed to do before netbox can be added to the p= orts tree.=20 An possible approach follows (option A from my initial comment in this PR) = for the ports - www/py-django-cors-headers - www/py-django-mptt - www/py-django-js-asset and their respective dependencies that needs to be adjusted/updated. At first here's an overview of the current situation (the dependendies that= are not related/bound to Django were left out for the sake of brevity): Dependencies with www/py-django-cors-headers: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For port www/py-django-cors-headers: > www/py-django-annotations (TODO: assign to www/py-django111 and www/djang= orestframework, upstream project seems stale...) > | > +--www/py-django-cors-headers (TODO: assign to www/py-django111) > | > +--www/py-djangorestframework36 > | > +--devel/py-django-rq (TODO: assign to www/py-django111) > | | > | `--www/py-django18 > | > `--devel/py-django-rq-dashboard (TODO: update to 0.3.3) > | > `--devel/py-django-rq Proposed plan for www/py-django-cors-headers (1 or 2 patches) would be roug= hly: 1. update devel/py-django-rq-dashboard to 0.3.3 (requires maintainer feedba= ck -> swills) 2. - change RUN_DEPENDS of devel/py-django-rq and www/py-django-cors-header= s -> www/py-django111 - change RUN_DEPENDS of www/py-django-annotations -> www/py-djangorestframework Dependencies with www/py-django-mptt and www/py-django-js-asset: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For port www/py-django-cms: > www/py-django-cms (TODO: update to 3.5.2 and assign to www/py-django111) > | > +--www/py-django18=20 > | > +--www/py-django-classy-tags (TODO: assign to/py-django18) > | | > | `--www/py-django18 > | > +--www/py-django-mptt (TODO: assign to www/py-django111 and www/py-djang= o-js-asset) > | | > | +--www/py-django18 > | | > | `--www/py-django-js-asset (TODO: assign to www/py-django111) > | | > | `--www/py-django18 > | > | > `--www/py-django-sekizai (TODO: update to 0.10.0 and assign to www/py-dja= ngo111) > | > +--devel/py-django18 > | > `--www/py-django-classy-tags (TODO: assign to www/py-django18) > | > `--www/py-django18 For port www/py-django-dpaste: > www/py-django-dpaste (TODO: update to 2.13a and assign to www/py-django11= 1) > | > +--www/py-django18 > | > `--www/py-django-mptt (TODO: assign to www/py-django111 and www/py-django= -js-asset) > | > +--www/py-django18 > | > `--www/py-django-js-asset (TODO: assign to www/py-django111) > | > `--www/py-django18 Proposed plan for www/py-django-cms and www/py-django-dpaste (one whole pat= ch) would be roughly: 1. - update www/py-django-sekizai to 0.10.0 and change RUN_DEPENDS to www/py-django111 (requires maintainer feedback -> xenophon+fbsdports@irtnog.org) - change RUN_DEPENDS of www/py-django-classy-tags to www/py-django111 - change RUN_DEPENDS of www/py-django-mptt to www/py-django111 - change RUN_DEPENDS of www/py-django-js-asset to www/py-django111 and www/py-django-mptt - update www/py-django-cms to 3.5.2 and change RUN_DEPENDS to www/py-django111 (requires maintainer feedback -> cs) - update www/py-django-dpaste to 2.13a and change RUN_DEPENDS to www/py-django111 (requires maintainer feedback -> koobs) If the whole approach sounds reasonable for all parties I would create the appropriate patches (and PRs, if required) for it. --=20 You are receiving this mail because: You are on the CC list for the bug.=