Re: Python 2.7 removal outline

2021-03-26 Thread Chris
On 2021-03-26 15:18, Olivier Certner wrote: Le vendredi 26 mars 2021, 22:43:12 CET Chris a écrit : Honestly. If something "just works", isn't a "security risk". Than don't fix it! Not so simple... But for build-only dependencies, I concur. But anyway, all new security reports for 3.x will

Re: Proposed ports git transition schedule

2021-03-26 Thread Felix Palmen
* Bob Eager [20210326 20:22]: > Felix Palmen wrote: > > I don't get what you mean. Repo details? A URL. > > With portsnap, I don't need a URL. It's built in. And that would be > nice. Ever had a look in /etc/portsnap.conf? Although it only wants a server name (well, mu

Re: Python 2.7 removal outline

2021-03-26 Thread Olivier Certner
Le vendredi 26 mars 2021, 22:43:12 CET Chris a écrit : > Honestly. If something "just works", isn't a "security risk". Than don't fix > it! Not so simple... But for build-only dependencies, I concur. But anyway, all new security reports for 3.x will be fixed in Tauthon. I've now already

Re: Python 2.7 removal outline

2021-03-26 Thread Chris
On 2021-03-26 12:19, Dan Mahoney (Ports) wrote: More thoughts on mailman, specifically: So, I just went to find an old FB post I made about mailman 2.x: === From the "Load Bearing Bit" department: Pretty much the entire world is stuck using an EOL'd mailing list manager (mailman 2.x),

Re: Proposed ports git transition schedule

2021-03-26 Thread Bob Eager
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 26 Mar 2021 19:30:03 +0100 Felix Palmen wrote: > * Bob Eager [20210326 14:27]: > > On Fri, 26 Mar 2021 14:04:17 +0100 > > Felix Palmen wrote: > > > I never used portsnap, but I'd assume net/gitup should serv

Re: Python 2.7 removal outline

2021-03-26 Thread Bob Eager
On Fri, 26 Mar 2021 14:55:15 -0500 Greg Rivers via freebsd-ports wrote: > On Friday, 26 March 2021 14:19:20 CDT Dan Mahoney (Ports) wrote: > > More thoughts on mailman, specifically: > > > > So, I just went to find an old FB post I made about mailman 2.x: > > > > === > > From the "Load Bearing

Re: Python 2.7 removal outline

2021-03-26 Thread Bob Eager
On Fri, 26 Mar 2021 09:06:08 -0700 Chris wrote: > > I doubt that meaning of overlay is going to be relevant. I'd not > > heard of it either, but from looking in ports/Mk/ it seems to be a > > way of modifying port builds. > As I understand it. It allows you to graft out-of-tree ports/versions

Re: Python 2.7 removal outline

2021-03-26 Thread Greg Rivers via freebsd-ports
On Friday, 26 March 2021 14:19:20 CDT Dan Mahoney (Ports) wrote: > More thoughts on mailman, specifically: > > So, I just went to find an old FB post I made about mailman 2.x: > > === > From the "Load Bearing Bit" department: > Pretty much the entire world is stuck using an EOL'd mailing

Re: Python 2.7 removal outline

2021-03-26 Thread Dan Mahoney (Ports)
More thoughts on mailman, specifically: So, I just went to find an old FB post I made about mailman 2.x: === From the "Load Bearing Bit" department: Pretty much the entire world is stuck using an EOL'd mailing list manager (mailman 2.x), which depends on an EOL'd python (2.7). This

Re: Proposed ports git transition schedule

2021-03-26 Thread Christoph Moench-Tegeder
## Felix Palmen (fe...@palmen-it.de): > I'd assume (someone may correct me) that portsnap will still be > supported, https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119098.html Regards, Christoph -- Spare Space ___

Re: Proposed ports git transition schedule

2021-03-26 Thread Felix Palmen
* Bob Eager [20210326 14:27]: > On Fri, 26 Mar 2021 14:04:17 +0100 > Felix Palmen wrote: > > I never used portsnap, but I'd assume net/gitup should serve the same > > usecase. > > > > Probably. So would git. Only that net/gitup is very lightweight and doesn't u

Re: Python 2.7 removal outline

2021-03-26 Thread Chris
On 2021-03-26 08:44, RW via freebsd-ports wrote: On Fri, 26 Mar 2021 13:55:33 +1100 (EST) Dave Horsfall wrote: On Thu, 25 Mar 2021, George Mitchell wrote: >> [...] it is really not for everybody to use overlays in current >> state (overlays are poor documented at least). [...] > > Until this

Re: Python 2.7 removal outline

2021-03-26 Thread RW via freebsd-ports
On Fri, 26 Mar 2021 13:55:33 +1100 (EST) Dave Horsfall wrote: > On Thu, 25 Mar 2021, George Mitchell wrote: > > >> [...] it is really not for everybody to use overlays in current > >> state (overlays are poor documented at least). [...] > > > > Until this thread I had never heard of them.

Re: Proposed ports git transition schedule

2021-03-26 Thread Bob Eager
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 26 Mar 2021 14:04:17 +0100 Felix Palmen wrote: > * Bob Eager [20210326 09:22]: > > Thanks for this. The documentation (although introductory) is quite > > detailed. What would be useful is just to note down the exact

Re: Proposed ports git transition schedule

2021-03-26 Thread Felix Palmen
* Bob Eager [20210326 09:22]: > Thanks for this. The documentation (although introductory) is quite > detailed. What would be useful is just to note down the exact > replacement for: > > portsnap fetch > portsnap extract I never used portsnap, but I'd assume net/gitup sho

Re: Proposed ports git transition schedule

2021-03-26 Thread Bob Eager
On Thu, 25 Mar 2021 21:56:03 -0400 Ed Maste wrote: > When the conversion is complete, Subversion will become read-only with > no further updates to the ports tree. If you are fetching ports using > svn, you will need to switch to the new git repository at the > following URLS: > > Web

Re: multimedia/gstreamer1 build error

2021-03-26 Thread Janos Dohanics
On Thu, 18 Mar 2021 14:25:40 -0400 Janos Dohanics wrote: > Hello, > > I have a laptop with FreeBSD 13.0-RC2 amd64 GENERIC 1300139 > 210a1aa0399bb8edf2d74f13171a400c613bee80 and a fully updated ports > tree. > > I get an error when building multimedia/gstreamer1: > > # make

Re: Python 2.7 removal outline

2021-03-26 Thread Chris
On 2021-03-25 22:24, Kurt Jaeger wrote: Hi! Why does our work have so little value that portmgr@ is unwilling to keep us all in the loop, or consider our opinions on such matters? The portmgr@ role is a huge task and all the reasons (limited time, dayjobs, etc) ares valid for those folks