public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Alex Schuilenburg <alexs@ecoscentric.com>
To: ecos-maintainers@ecos.sourceware.org
Subject: Bugzilla new accounts working again
Date: Wed, 17 Feb 2010 13:19:00 -0000	[thread overview]
Message-ID: <4B7BECC9.70106@ecoscentric.com> (raw)

Hi

Unfortunately the public creation of new bugzilla email accounts (i.e.
by non-maintainers) on bugs.ecos.sourceware.org was broken from around
8th Jan when Red Hat in their wizdom (sic) changed SE linux settings
which broke postfix
(https://bugzilla.redhat.com/show_bug.cgi?id=553492).  While I picked up
this error fairly quickly and had my own patch in place well before Red
Hat pushed out their own fix, I forgot to test Bugzilla when Red Hat
finally caved and pushed out an update of their own.  Their fix is not
far reaching enough and while it works in most circumstances, it does
not work for bugzilla.

I have a work-around in place and will leave it installed.  Please do
not change any of the email settings in the bugzilla configuration else
you may break email again :-(  I will try and chase up a permanent fix
with Red Hat.

Motto: If it ain't broke, don't fix it!!!

Cheers

-- Alex Schuilenburg
Managing Director/CEO                                eCosCentric Limited
Tel:  +44 1223 245571                     Barnwell House, Barnwell Drive
Fax:  +44 1223 248712                             Cambridge, CB5 8UU, UK
www.ecoscentric.com             Reg in England and Wales, Reg No 4422071

Besuchen Sie uns vom 2-4 März auf der Embedded World 2010, Stand 11-208
Visit us at Embedded World 2010, Nürnberg-Germany, 2-4 Mar, Stand 11-208



                 reply	other threads:[~2010-02-17 13:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4B7BECC9.70106@ecoscentric.com \
    --to=alexs@ecoscentric.com \
    --cc=ecos-maintainers@ecos.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).