Re: [NEW PORT] PyCharm Professional
Hi! > Would someone please commit this new port to the ports tree? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242705 Done. -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: py37-certbot-1.5.0_1,1
On Fri, Jul 10, 2020 at 02:32:42PM +0200, Ruud Boon wrote: > Hi, > > Thank you for maintain this port. > Any plans bumping to 1.6.0 soon? Hi. Done. https://svnweb.freebsd.org/changeset/ports/542003 If you are using pkg you will need to wait for the package. Regards. -- Danilo G. Baio (dbaio) signature.asc Description: PGP signature
Re: bugzilla messages about issues related to freebsd-ports, freebsd-multimedia, ...
Hi! > why as MAINTAINER a full discussion(!) mailing list is used? Having individuals as maintainers can cause delays in approving patches and providing updates. So at some time in the past, some groups of port maintainers choose to band together and have a mailing list -- and changed the MAINTAINER to the list, so that each member of the list could update the port, if it was needed. This can cause other delays, because no-one might feel responsible for a port, so recently, bugmeister@ choose to add (Nobody) to some of the group maintainers, so that others do not wait for group approval. It's a problem of assigning some feel of 'ownership and responsibility' on the one hand and delegation on the other. I take it from your question that you feel this is not a good solution... -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[NEW PORT] PyCharm Professional
Hi, Would someone please commit this new port to the ports tree? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242705 Short recap: - it's based on the existing port devel/pycharm-e - it's marked RESTRICTED as its license does not allow redistribution (still waiting for an approval from Jetbrains) - I've been using the port successfully for the past half year. - files/pkg-message.in documents things to be aware of Cheers, Guido ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: bugzilla messages about issues related to freebsd-ports, freebsd-multimedia, ...
El día sábado, julio 11, 2020 a las 04:35:10a. m. -0700, David Wolfskill escribió: > On Sat, Jul 11, 2020 at 01:27:55PM +0200, Matthias Apitz wrote: > > ... > > There is nothing written about "... and for Cc issues from bugzilla". > > > > What I do not like and do not understand why this was introduced, that > > the issue tracker bugzilla copies comments etc. in the issues to the > > mailing-list and spams the lists with this (an example is below). This > > way I get every day some hundred mails. > > > > Why is this intention? Can it be changed? To whom I should direct this > > complain? > > > > matthias > > > > > That happens -- at least in the case of multimedia/ffmpeg -- because: > > g1-55(13.0-C)[4] awk -F = '$1 == "MAINTAINER"' > /usr/ports/multimedia/ffmpeg/Makefile > MAINTAINER= multime...@freebsd.org > > So it's merely notification to the listed "maintainer" of the port. I know, and then the question is: why as MAINTAINER a full discussion(!) mailing list is used? matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub May, 9: Спаси́бо освободители! Thank you very much, Russian liberators! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: bugzilla messages about issues related to freebsd-ports, freebsd-multimedia, ...
On Sat, Jul 11, 2020 at 01:27:55PM +0200, Matthias Apitz wrote: > ... > There is nothing written about "... and for Cc issues from bugzilla". > > What I do not like and do not understand why this was introduced, that > the issue tracker bugzilla copies comments etc. in the issues to the > mailing-list and spams the lists with this (an example is below). This > way I get every day some hundred mails. > > Why is this intention? Can it be changed? To whom I should direct this > complain? > > matthias > That happens -- at least in the case of multimedia/ffmpeg -- because: g1-55(13.0-C)[4] awk -F = '$1 == "MAINTAINER"' /usr/ports/multimedia/ffmpeg/Makefile MAINTAINER= multime...@freebsd.org So it's merely notification to the listed "maintainer" of the port. Peace, david -- David H. Wolfskill da...@catwhisker.org If Trump continues to delay access to his tax records, a voter would be prudent to presume that they contain incriminating information. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
bugzilla messages about issues related to freebsd-ports, freebsd-multimedia, ...
Hello, I'm subscribed to a bunch of mailings list, for example freebsd-multimedia@ and freebsd-ports@, to ask there from time a question or to follow discussion on topics I'm interested in. And this is exactly for what the mailing-lists are designed for, if you check in the mailman server their purpose: About freebsd-ports Discussions concerning FreeBSD's "ports collection" (/usr/ports), proposed ports, modifications to ports collection infrastructure and general coordination efforts. About freebsd-multimedia This is a forum about multimedia applications using FreeBSD. Discussion center around multimedia applications, their installation, their development and their support within FreeBSD There is nothing written about "... and for Cc issues from bugzilla". What I do not like and do not understand why this was introduced, that the issue tracker bugzilla copies comments etc. in the issues to the mailing-list and spams the lists with this (an example is below). This way I get every day some hundred mails. Why is this intention? Can it be changed? To whom I should direct this complain? matthias - Forwarded message from bugzilla-nore...@freebsd.org - Date: Sat, 11 Jul 2020 10:47:05 + From: bugzilla-nore...@freebsd.org To: multime...@freebsd.org Subject: [Bug 247873] multimedia/ffmpeg: SVT patches are broken at fetch https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247873 --- Comment #6 from Jan Beich --- Cannot be fixed (without a lot of churn) yet because SVT-VP9 upstream introduced an incompatible change *before* fixing compatibility with SVT-AV1 v0.8.4. Unfortunately, after bug 246789 it's not possible to sacrifice only SVTVP9 option. https://github.com/OpenVisualCloud/SVT-VP9/issues/124 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-multime...@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-multimedia To unsubscribe, send any mail to "freebsd-multimedia-unsubscr...@freebsd.org" - End forwarded message - -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub May, 9: Спаси́бо освободители! Thank you very much, Russian liberators! signature.asc Description: PGP signature
Re: MOVED format error
Hi, This night's svn up fixes the problem. Thanks Xavier On 10/07/2020 07:09, Pau Amma wrote: > On 2020-07-10 06:54, Xavier Humbert wrote: >> Hello, >> >> Apparently the MOVED file is broken : > > Maybe fixed in > https://svnweb.freebsd.org/ports?view=revision&revision=541808 ? > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
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 can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ science/afni| 20.2.00 | afni_20.2.01 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
