https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185884
Kubilay Kocak <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected], | |[email protected], | |[email protected] 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 <[email protected]> --- @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 noticed 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 probably 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, it's important to create an issue per port (for port changes), or an issue per isolated/standalone change, so that individual maintainers can be automatically 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. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ kde-freebsd mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
