From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: overseers@sourceware.org, Florian Weimer <fweimer@redhat.com>
Subject: Re: Choice of distribution for new sourceware.org server?
Date: Thu, 06 Feb 2020 06:05:00 -0000 [thread overview]
Message-ID: <20200206060547.GA1868@cgf.cx> (raw)
In-Reply-To: <bf2e3d28-2ff6-6052-a029-d0548eacb740@redhat.com>
On Wed, Feb 05, 2020 at 08:45:28PM -0500, Carlos O'Donell wrote:
>Otherwise dog-fooding Fedora Server would give us the latest packages
>for services that sourceware could offer, but we'd have to update once
>a year.
We talk about that every time we go through a system or OS upgrade.
I've maintained a postfix/mailman system in the past so maybe those bits
would swap back in. I don't really relish the thought of trying to
convert the ezmlm archives to something else but maybe it isn't a big
deal.
>It would force us to actively track the software we're using and look
>at well supported alternatives e.g. postfix + mailman/public inbox vs.
>qmail + ezmlm.
I use Rawhide on some of my systems and rarely have had a problem but I
can hear the screams now.
Upgrading to the next version only requires minimal downtime though.
So, I'd still be happy to be using it. I assume we can get the same
level of input from Red Hat if we have kernel issues.
This is the third or fourth time I've moved to a new version of
qmail/ezmlm and I never have a good feeling about it since the available
rpms always seem a little odd. They have dependencies on things that I
don't really understand like "vpopmail". We could roll our own like
we did when sourceware was new but that means being diligent about
security issues.
I think I've just convinced myself to look into using postfix and
mailman. I'll try to do that in the next few days.
cgf
next prev parent reply other threads:[~2020-02-06 6:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 1:05 Carlos O'Donell
2020-02-06 1:30 ` Christopher Faylor
2020-02-06 1:34 ` Frank Ch. Eigler
2020-02-06 1:51 ` Carlos O'Donell
2020-02-06 2:02 ` Frank Ch. Eigler
2020-02-06 2:16 ` Carlos O'Donell
2020-02-06 14:49 ` Frank Ch. Eigler
2020-02-06 15:10 ` Carlos O'Donell
2020-02-06 15:19 ` Frank Ch. Eigler
2020-02-06 16:36 ` Carlos O'Donell
2020-02-06 16:46 ` Christopher Faylor
2020-02-06 16:49 ` Frank Ch. Eigler
2020-02-06 1:45 ` Carlos O'Donell
2020-02-06 6:05 ` Christopher Faylor [this message]
2020-02-06 14:50 ` Carlos O'Donell
2020-02-06 15:11 ` Lukas Berk
2020-02-06 15:22 ` Carlos O'Donell
2020-02-06 15:20 ` Christopher Faylor
2020-02-06 17:05 ` Carlos O'Donell
2020-02-06 18:28 ` Joseph Myers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200206060547.GA1868@cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).