Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Feb 2016 14:51:18 +0000
From:      bugzilla-noreply@freebsd.org
To:        python@FreeBSD.org
Subject:   [Bug 185884] devel/llvm32, devel/py-qt4, emulators/virtualbox-ose: Python 3 fixes
Message-ID:  <bug-185884-21822-OsuHbY2T2k@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-185884-21822@https.bugs.freebsd.org/bugzilla/>
References:  <bug-185884-21822@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D185884

Kubilay Kocak <koobs@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |brooks@FreeBSD.org,
                   |                            |kde@FreeBSD.org,
                   |                            |vbox@FreeBSD.org
           Keywords|easy, patch-ready           |
            Summary|Miscellaneous ports fixes   |devel/llvm32, devel/py-qt4,
                   |for Python 3                |emulators/virtualbox-ose:
                   |                            |Python 3 fixes
              Flags|                            |maintainer-feedback?(kde@Fr
                   |                            |eeBSD.org)

--- Comment #8 from Kubilay Kocak <koobs@FreeBSD.org> ---
@Alfred I'm not sure this change comes under python@ domain, since it makes
changes to ports not maintained by the python team. I should/could have not=
iced
this when canonicalising the python@ assignment, but did not inspect the
attachment contents at the time.

On first look however it appears that a few updates to the patches are prob=
ably
necessary, in terms of:

* that the reported issues are still present in the ports
* if so, ensuring the diffs still apply (and are valid) against ports head
* that any python framework changes that have occurred since submission are
reflected. For instance, PYTHON_PY3K_PLIST_HACK has been removed.

To ensure that future issues don't fall through the cracks like this one, i=
t's
important to create an issue per port (for port changes), or an issue per
isolated/standalone change, so that individual maintainers can be automatic=
ally
informed and assigned.

I have cc'd the relevant maintainers on this issue now, though 'assignment'=
 is
the primary way committers (particularly those in teams@) track their open =
task
lists.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-185884-21822-OsuHbY2T2k>