If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Status

Infrastructure & Operations
Infrastructure: Other
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: justdave, Assigned: mburns)

Tracking

Details

issues with our in-house mailman SRPM that I need to fix:

1) mozcss directory gets wrong permissions and isn't readable by the webserver

2) /var/lock/mailman directory isn't created, which causes mailman to fail to start until it gets created.
3) /var/run/mailman directory isn't created.
4) python 2.6 chokes on undeclared utf-8 content.  The default mm_cfg.py needs the following line added at the top of it:

# -*- coding: utf-8 -*-
5) /var/lib/mailman/archives/private gets created as 2775 mailman:apache, this causes lists created via the web interface to be unwritable by the archiver. It should be 2775 apache:mailman <- this is probably an upstream bug in RedHat's Mailman package
(Assignee)

Updated

5 years ago
Blocks: 770423
(Assignee)

Comment 4

5 years ago
In builing a new mailman rpm, I've gotten myself acquainted with the SPEC file and the directory structure it defines. I can include these changes.
Assignee: justdave → mburns
Status: NEW → ASSIGNED
(Assignee)

Updated

5 years ago
Blocks: 765289
(Assignee)

Comment 5

5 years ago
1-3 were in place. I've finished 4 and 5.

1. done "- fix perms on mozcss directory the correct way"
2. done %define lockdir /var/lock/%{name}
3. done %define piddir /var/run/%{name}

4. bug 815466 caught any last non-utf-8 declaring stragglers.

5. This is currently out of sync with comment 3 . I'll confirm this in staging and revert if needed. Would need a chown or puppet permission rule to migrate to.

ls -lh /var/lib/mailman/archives/private/foobar
drwxrwsr-x    9 apache mailman 4.0K Apr 1  03:27 foobar

SPEC/mailman.spec:
%attr(2770, apache,  mailman) %{archivesdir}/private
%attr(2770, mailman, apache)  %{archivesdir}/private
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Component: Server Operations: Infrastructure → Infrastructure: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.