On 27/03/21 12:42, Guido Falsi via freebsd-ports wrote:
On 27/03/21 10:44, Anatoly wrote:
On Thu, 25 Mar 2021 23:06:27 -0700
Chris wrote:
On 2021-03-25 22:24, Kurt Jaeger wrote:
The portmgr@ role is a huge task and all the reasons (limited time,
dayjobs, etc) ares valid for those folks fr
On 27/03/21 10:44, Anatoly wrote:
On Thu, 25 Mar 2021 23:06:27 -0700
Chris wrote:
On 2021-03-25 22:24, Kurt Jaeger wrote:
The portmgr@ role is a huge task and all the reasons (limited time,
dayjobs, etc) ares valid for those folks from portmgr as for
the rest of the ports maintainers and c
On Thu, 25 Mar 2021 23:06:27 -0700
Chris wrote:
> On 2021-03-25 22:24, Kurt Jaeger wrote:
> > The portmgr@ role is a huge task and all the reasons (limited time,
> > dayjobs, etc) ares valid for those folks from portmgr as for
> > the rest of the ports maintainers and committers.
> Indeed, an
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 be
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 reviewed
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), whi
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
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
>
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 list
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 include
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 t
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.
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 fro
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 from portmgr as for
the rest of the ports m
There have been a great many comments on this matter on the
mailing list. All the replies are valuable. But (this) original
post has been trimmed in all those replies. So in an effort to
maintain context to the original statement. I'm making my reply
here. Which reflects the attitude of most all o
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. -- George
I can't remember the last time I used overlays (certainly w
On 26/03/2021 9:25 am, George Mitchell wrote:
> On 3/25/21 6:06 PM, Miroslav Lachman 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. -- George
On 3/25/21 6:06 PM, Miroslav Lachman 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. -- George
OpenPGP_signature
Description: OpenPGP digital signature
On 25/03/2021 16:03, Baptiste Daroussin wrote:
I will only here answer about the quality of the communication of portmgr, yes
there is room of improvement in general in the current portmgr team as of how we
do communicate about plans and policy and we are working on it.
"There is room of impro
I find this announcement very much disappointing, because the situation for
ports that need Python 2.7 or similar to build doesn't seem to have changed at
all. In short, we are just told (again) that they should disappear.
Many end-users who maintain python2 code, both application and install
de
Am 24.03.21 um 23:11 schrieb Matthias Andree:
> Am 24.03.21 um 22:50 schrieb Dan Mahoney (Ports):
>
>> There are packages for mailman3 but they’re incomplete and don’t
> result in a working install the way the 2.x build does. You also need
> mysql, django, etc etc.
>
> Dan, please check if we alre
Am 25.03.21 um 16:03 schrieb Baptiste Daroussin:
>
> I really think we should as a project move forward to that direction, it does
> not even need to be driven by protmgr or even drive by any @freebsd.org
>
> I would argue here that it is even more interesting to go the gentoo way try
> to
> provi
I meant to send this reply to the list. I beg for @bapt's forgiveness
for the inbox echo.
On 3/25/21 8:03 AM, Baptiste Daroussin wrote:
> On Thu, Mar 25, 2021 at 12:02:29PM +0100, Olivier Certner wrote:
>>
>> 2. Leverage overlays to provide additional repos, a bit like AUR for Arch.
>> Here I'm i
On Thu, Mar 25, 2021 at 12:02:29PM +0100, Olivier Certner wrote:
> Hi,
>
> Maintainer of Tauthon here, and of Pale Moon (for the few hours it lived in
> the tree in February; but I'm still pushing updates to PR 251117).
>
> I find this announcement very much disappointing, because the situation
Hi,
Maintainer of Tauthon here, and of Pale Moon (for the few hours it lived in
the tree in February; but I'm still pushing updates to PR 251117).
I find this announcement very much disappointing, because the situation for
ports that need Python 2.7 or similar to build doesn't seem to have chan
On 25/03/2021 07:26, Dewayne Geraghty wrote:
On 25/03/2021 4:01 am, Miroslav Lachman wrote:
I really appreciate the work of ports team, committers and maintainers
but I dislike double standards. All ports requiring Python 2.7 were
marked deprecated the last year almost all of them removed accor
On 24/3/21 22:50, Dan Mahoney (Ports) wrote:
> There are packages for mailman3 but they’re incomplete and don’t
result in a working install the way the 2.x build does. You also need
mysql, django, etc etc.
>
> Needing django is almost as bad as saying “sure, the web UI depends
on WordPress”.
On 25/03/2021 4:01 am, Miroslav Lachman wrote:
> I really appreciate the work of ports team, committers and maintainers
> but I dislike double standards. All ports requiring Python 2.7 were
> marked deprecated the last year almost all of them removed according to
> expiration date 2020-12-31 but s
Am 24.03.21 um 22:50 schrieb Dan Mahoney (Ports):
> There are packages for mailman3 but they’re incomplete and don’t
result in a working install the way the 2.x build does. You also need
mysql, django, etc etc.
Dan, please check if we already have bug reports on the mailman 3 issues
and where th
Am 24.03.21 um 14:03 schrieb Rene Ladan:
> Hi,
>
> below is an outline continuing the Python 2.7 cleanup:
>
> - No usage of lang/tauthon by the framework or any port, no excuses.
> - lang/tauthon will be removed on 2021-06-23 as noticed in the port
> itself,
> no excuses. Tauthon is not guarantee
Am 24.03.21 um 22:48 schrieb Baptiste Daroussin:
> On Wed, Mar 24, 2021 at 09:45:09PM +, Bob Eager wrote:
>> On Wed, 24 Mar 2021 13:03:47 +
>> Rene Ladan wrote:
>>
>>> - - mail/mailman is being replaced by clusteradm@ with mlmmj. You
>>> can use `pkg lock` to stick with it after removal,
There are packages for mailman3 but they’re incomplete and don’t result in a
working install the way the 2.x build does. You also need mysql, django, etc
etc.
Needing django is almost as bad as saying “sure, the web UI depends on
WordPress”. It’s not standalone cgi’s that you can just scripta
On Wed, Mar 24, 2021 at 09:45:09PM +, Bob Eager wrote:
> On Wed, 24 Mar 2021 13:03:47 +
> Rene Ladan wrote:
>
> > - - mail/mailman is being replaced by clusteradm@ with mlmmj. You
> > can use `pkg lock` to stick with it after removal, if there is no
> > other way.
>
> Is anyone working
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 24 Mar 2021 13:03:47 +
Rene Ladan wrote:
> - - mail/mailman is being replaced by clusteradm@ with mlmmj. You
> can use `pkg lock` to stick with it after removal, if there is no
> other way.
Is anyone working on a mailman 3 port?
-
On 24/03/21 14:03, Rene Ladan wrote:
Hi,
below is an outline continuing the Python 2.7 cleanup:
- all affected ports are now marked as deprecated, with an expiration date
of either 2020-12-31 or 2021-06-23.
- we will have to wait for Chromium to fully switch to Python 3 before we
can full
On 24/03/2021 14:03, Rene Ladan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
below is an outline continuing the Python 2.7 cleanup:
- - all affected ports are now marked as deprecated, with an expiration date
of either 2020-12-31 or 2021-06-23.
- - we will have to wait for Chr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
below is an outline continuing the Python 2.7 cleanup:
- - all affected ports are now marked as deprecated, with an expiration date
of either 2020-12-31 or 2021-06-23.
- - we will have to wait for Chromium to fully switch to Python 3 before w
37 matches
Mail list logo
