Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 88144 - Upgrading to RedHat 9 causes all mailing list archives to point to http://porky.devel.redhat.com/...
Upgrading to RedHat 9 causes all mailing list archives to point to http://por...
Product: Red Hat Linux
Classification: Retired
Component: mailman (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: John Dennis
Depends On:
  Show dependency treegraph
Reported: 2003-04-06 16:15 EDT by H. Peter Anvin
Modified: 2007-04-18 12:52 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-04-24 11:15:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2003:179 normal SHIPPED_LIVE Mailman RPM does not properly handle package installation and upgrade. 2003-09-24 00:00:00 EDT

  None (edit)
Description H. Peter Anvin 2003-04-06 16:15:31 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030211

Description of problem:
The shipped Mailman/Defaults.py contains:

DEFAULT_EMAIL_HOST = 'porky.devel.redhat.com'
DEFAULT_URL_HOST = 'porky.devel.redhat.com'

After doing an upgrade from RedHat 8.0, this causes *ALL* mailing list archive
links to point to http://porky.devel.redhat.com/... instead of using the web URL
that is assigned to each mailing list.  I have worked around this by adding in


... however, that is less desirable than the previous situation since it will no
longer point to the correct vhost.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Set up a Mailman server on RedHat 8
2. Upgrade to RedHat 9
3. Fix the problems described in bug 88083
4. Go to http://<host>/mailman/listinfo/<listname>
5. Click on the archive link

Actual Results:  Attempt to open http://porky.devel.redhat.com/pipermail/...

Expected Results:  Attempt to open http://<host>/pipermail/...

Additional info:
Comment 1 Jean-Baptiste Vignaud 2003-04-10 17:29:09 EDT
I have fixed 88083 on my upgraded server and i have some more information on
this problem:

I have two lists on my server; one list is public, it's name is displayed with
the other is private and does not appear.

I reproduce the problem only with the public list. The private one is working
fine and leads to
Comment 2 SEKINE Tatsuo 2003-04-23 23:13:32 EDT
The reason of this problem is that
  /var/mailman/Mailman/mm_cfg.py is NOT marked as config file.

Please run the command below:
  $ rpm -q --qf \
    "[%{FILENAMES} (%{FILEFLAGS:fflags})\n]" mailman \
    | grep mm_cfg

The result should be
  /var/mailman/Mailman/mm_cfg.py (cn)
where "c" means "config" and "n" mesans "noreplace",
but we obtain
  /var/mailman/Mailman/mm_cfg.py ()

The spec file shoud have
  %attr(0644, root, mailman) %config(noreplace) \
  %verify(not md5 size time) %{_var}/mailman/Mailman/mm_cfg.py

Obviously this CRITICAL bug cause many problems.
- Updating destroy old configuration.
- Verifying of package will fail always.
- etc.
Comment 3 John Dennis 2003-09-24 15:18:33 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.