Bug 1008139
Summary: | rmlist fails if list_data_dir is not a child of var_prefix | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Nic Waller <nicwaller> |
Component: | mailman | Assignee: | Jan Kaluža <jkaluza> |
Status: | CLOSED ERRATA | QA Contact: | Alois Mahdal <amahdal> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4 | CC: | amahdal, psklenar |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | mailman-2.1.12-20.el6 | Doc Type: | Bug Fix |
Doc Text: |
The "rmlist" command used a hardcoded path to list data based on the VAR_PREFIX configuration variable. As a consequence, when the list was created outside of VAR_PREFIX, it was impossible to remove it using the "rmlist" command. With this update, the "rmlist" command uses the correct LIST_DATA_DIR value instead of VAR_PREFIX, and it is now possible to remove the list in described situation.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-07-22 07:41:48 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nic Waller
2013-09-15 07:04:06 UTC
Thanks for the report. This can be fixed by following upstream patch: http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1273 This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux. Verified on all supported architectures Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1417.html |