[Bug 230760] databases/py-sqlite3 - USES=python:37 fails with wrong file name

2018-08-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230760 Yasuhito FUTATSUKI changed: What|Removed |Added CC||freebsd-bug-report...@yf.bs

[Bug 229562] lang/python37: Fails to build when misc/e2fsprogs-libuuid is installed (conflicts with base)

2018-08-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229562 --- Comment #7 from Yasuhito FUTATSUKI --- Same issue at upstream (with pull request to fix it) https://bugs.python.org/issue34366 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the b

[Bug 230760] databases/py-sqlite3 - USES=python:37 fails with wrong file name

2018-08-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230760 Bug ID: 230760 Summary: databases/py-sqlite3 - USES=python:37 fails with wrong file name Product: Ports & Packages Version: Latest Hardware: amd64 OS:

maintainer-feedback requested: [Bug 230760] databases/py-sqlite3 - USES=python:37 fails with wrong file name

2018-08-19 Thread bugzilla-noreply
Bugzilla Automation has asked freebsd-python mailing list for maintainer-feedback: Bug 230760: databases/py-sqlite3 - USES=python:37 fails with wrong file name https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230760 --- Description --- when building with: make USES=python:3.7 install fails

Problem reports for pyt...@freebsd.org that need special attention

2018-08-19 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 230754] security/py-pycryptodome: Upgrade to 3.6.6

2018-08-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230754 Sunpoet Po-Chuan Hsieh changed: What|Removed |Added Resolution|--- |FIXED Status|

[Bug 230754] security/py-pycryptodome: Upgrade to 3.6.6

2018-08-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230754 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: sunpoet Date: Sun Aug 19 20:32:47 UTC 2018 New revision: 477598 URL: https://svnweb.freebsd.org/changeset/ports/477598 Log: Update to 3.6.6 Changes:

[Bug 230754] security/py-pycryptodome: Upgrade to 3.6.6

2018-08-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230754 Sunpoet Po-Chuan Hsieh changed: What|Removed |Added Assignee|ports-b...@freebsd.org |sunp...@freebsd.org -- Y

Maintainer timeout(-ish): security/py-kerberos bug 230385

2018-08-19 Thread John W. O'Brien
Hello FreeBSD Ports, Though he hasn't set the maintainer feedback flag to "+", Dan already gave an informal go-ahead ("please proceed with my approval"). Also, that was two weeks ago. Are there any committers within earshot able and willing to take this bug? [0] security/py-kerberos: Upgrade to

[Bug 230754] security/py-pycryptodome: Upgrade to 3.6.6

2018-08-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230754 John W. O'Brien changed: What|Removed |Added Attachment #196356||maintainer-approval+

[Bug 230754] security/py-pycryptodome: Upgrade to 3.6.6

2018-08-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230754 John W. O'Brien changed: What|Removed |Added CC||pyt...@freebsd.org Key

[Bug 227149] Use the www/py-django meta port instead of the www/py-django18 port to move to Django 1.11

2018-08-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227149 --- Comment #9 from commit-h...@freebsd.org --- A commit references this bug: Author: rene Date: Sun Aug 19 13:55:44 UTC 2018 New revision: 477575 URL: https://svnweb.freebsd.org/changeset/ports/477575 Log: www/py-django: remove support

FreeBSD ports you maintain which are out of date

2018-08-19 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you