On 2020-04-30 21:31, Julian H. Stacey wrote:
> [...]
> PS I've not the foggiest what Tauthon is , so searched
> https://en.wikipedia.org/wiki/Special:Search?search=Tauthon&go=Go&ns0=1
> The page "Tauthon" does not exist.
> cd /usr/ports ; cd */*tauthon* # */*tauthon*: No m
Matthias Andree wrote:
> Am 29.04.20 um 17:00 schrieb Julian H. Stacey:
> > Greg Veldman wrote ports@:
> >> On Tue, Apr 28, 2020 at 01:02:14PM -0700, Chris wrote:
> >>> It also wouldn't be that difficult to simply modify mailman(2)
> >>> to adopt the py3.x language changes.
> >>
> >> To simply make
On Thu, Apr 30, 2020 at 03:59:16AM +0200, Kurt Jaeger wrote:
> There are many thousand links to the freebsd pipermail archives,
> and invalidating all those links sounds like a serious loss of institutional
> memory.
>
> Is there a way to cope with that ? Some sort of
> lookup 'old link' -> 'new l
On Wed, Apr 29, 2020 at 07:56:08PM -0700, Chris wrote:
> I really like Perl a lot more for all this string/byte handling stuff.
> Maybe Majordomo? B-}
The latest release was two decades ago, not sure I'd go that
route. ;-) Sympa would probably be a better choice.
--
Greg Veldman
free...@gregv.n
>> AIUI you can move your entire archive to the new system.
>
> There are many thousand links to the freebsd pipermail archives,
> and invalidating all those links sounds like a serious loss of institutional
> memory.
As I said in the pat of my message you snipped, you do not have to remove your
On Thu, 30 Apr 2020 02:03:20 +0200 Matthias Andree matthias.and...@gmx.de said
Am 28.04.20 um 22:02 schrieb Chris:
> In sentiment I am inline with your thoughts as well.
> Would it be a worthy project to create a mailman(2)-lts port?
> I'd be fully up for helping, and or creating it myself.
> Th
Hi!
> On 28 Apr 2020, at 14:00, Chris wrote:
> > as at *least* it completely abandons the previous archive system.
>
> Pipermail was??? lacking. It looked 20 years old (because it was).
>
> > Making your previous archive, an archive of an archive.
>
> AIUI you can move your entire archive to t
On 28 Apr 2020, at 14:00, Chris wrote:
> as at *least* it completely abandons the previous archive system.
Pipermail was… lacking. It looked 20 years old (because it was).
> Making your previous archive, an archive of an archive.
AIUI you can move your entire archive to the new system. You can
Am 28.04.20 um 22:02 schrieb Chris:
> In sentiment I am inline with your thoughts as well.
> Would it be a worthy project to create a mailman(2)-lts port?
> I'd be fully up for helping, and or creating it myself.
> There's a port that's a shim for py2.x-->py3.x called 2to3, or something
> like that
Hi, Reference:
> From: Greg Veldman
> Date: Wed, 29 Apr 2020 12:33:42 -0400
Greg Veldman wrote:
> On Wed, Apr 29, 2020 at 05:00:01PM +0200, Julian H. Stacey wrote:
> > Even if it's possible to bend ports/mail/mailman to support Mailman3
> > Please do not do it; keep it clean for j
On Wed, Apr 29, 2020 at 05:00:01PM +0200, Julian H. Stacey wrote:
> Even if it's possible to bend ports/mail/mailman to support Mailman3
> Please do not do it; keep it clean for just Mailman2
> (Else it would cause big run time problems for user admins (inc. me)).
>
> Any who will want Mailman3 sh
Greg Veldman wrote ports@:
> On Tue, Apr 28, 2020 at 01:02:14PM -0700, Chris wrote:
> > It also wouldn't be that difficult to simply modify mailman(2)
> > to adopt the py3.x language changes.
>
> To simply make it work, perhaps not. To make it work well and
> be reliable... might be more difficul
On Tue, Apr 28, 2020 at 01:02:14PM -0700, Chris wrote:
> It also wouldn't be that difficult to simply modify mailman(2)
> to adopt the py3.x language changes.
To simply make it work, perhaps not. To make it work well and
be reliable... might be more difficult than you think. A large
chunk of wha
On Tue, 28 Apr 2020 17:33:41 +0200 Matthias Andree matthias.and...@gmx.de said
[Dan, Kurt, this is a re-send of my message written 2020-04-24 with a
different sender address.]
Am 24.04.20 um 15:04 schrieb Kurt Jaeger:
> Hi!
>
>> With mail/mailman being Python 2.7 (which is end-of-life), and mai
On Tue, 28 Apr 2020 16:43:49 +0200 Kurt Jaeger p...@freebsd.org said
Hi!
> I see the mailman lists themselves are now on Mailman 3:
>
>
>
https://mail.python.org/archives/list/mailman-annou...@python.org/thread/HHQN7V6NY7G5CTOSC3WBU7VXW5KEBGVO/
Interesting!
Looks like a very uncomfortable
On 28 Apr 2020, at 09:33, Matthias Andree wrote:
> Leaving Python 3.x compatibility aside,
But that is the main issue. Python 2.7 is dead. Well, fine, it’s not quite dead
yet, but it is also not feeling any better.
(I ran mailman lists for many years, but never made the move to mailman 3 and
t
Am 28.04.20 um 16:34 schrieb Dan Langille:
> On Fri, Apr 24, 2020, at 9:32 AM, Dan Langille wrote:
>>> On Apr 24, 2020, at 9:04 AM, Kurt Jaeger wrote:
>>>
>>> Hi!
>>>
With mail/mailman being Python 2.7 (which is end-of-life), and mailman 3
being Python 3 compatible:
Do you kno
[Dan, Kurt, this is a re-send of my message written 2020-04-24 with a
different sender address.]
Am 24.04.20 um 15:04 schrieb Kurt Jaeger:
> Hi!
>
>> With mail/mailman being Python 2.7 (which is end-of-life), and mailman 3
>> being Python 3 compatible:
>>
>> Do you know of any plans to port Mailm
Hi!
> I see the mailman lists themselves are now on Mailman 3:
>
> https://mail.python.org/archives/list/mailman-annou...@python.org/thread/HHQN7V6NY7G5CTOSC3WBU7VXW5KEBGVO/
Interesting!
Looks like a very uncomfortable design for uniq URLs 8-(
--
p...@freebsd.org +49 171 3101372
On Fri, Apr 24, 2020, at 9:32 AM, Dan Langille wrote:
> > On Apr 24, 2020, at 9:04 AM, Kurt Jaeger wrote:
> >
> > Hi!
> >
> >> With mail/mailman being Python 2.7 (which is end-of-life), and mailman 3
> >> being Python 3 compatible:
> >>
> >> Do you know of any plans to port Mailman 3?
> >
> >
> On Apr 24, 2020, at 9:04 AM, Kurt Jaeger wrote:
>
> Hi!
>
>> With mail/mailman being Python 2.7 (which is end-of-life), and mailman 3
>> being Python 3 compatible:
>>
>> Do you know of any plans to port Mailman 3?
>
> There's already a PR about that:
>
> https://bugs.freebsd.org/bugzilla/s
Hi!
> With mail/mailman being Python 2.7 (which is end-of-life), and mailman 3
> being Python 3 compatible:
>
> Do you know of any plans to port Mailman 3?
There's already a PR about that:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225543
The patch itself is fine, but we need run-tests
Hello Matthias,
With mail/mailman being Python 2.7 (which is end-of-life), and mailman 3 being
Python 3 compatible:
Do you know of any plans to port Mailman 3?
If you were planning to do that, I can help.
Thank you.
—
Dan Langille
http://langille.org/
___
23 matches
Mail list logo
