Bug 125628 - postfix 2.0 -> 2.1 upgrade warnings bogus
postfix 2.0 -> 2.1 upgrade warnings bogus
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: postfix (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Thomas Woerner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-06-09 11:17 EDT by Chris Ricker
Modified: 2008-05-09 13:34 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-06-21 08:24:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Ricker 2004-06-09 11:17:41 EDT
Upgrading from the postfix 2.0 RPM shipped in FC2 to the rawhide
postfix 2.1, I get

[root@knomta fc2]# rpm -Fvh postfix-2.1.1-1.i386.rpm
Preparing...               
########################################### [100%]
   1:postfix                warning: /etc/postfix/main.cf created as
/etc/postfix/main.cf.rpmnew
warning: /etc/postfix/master.cf created as /etc/postfix/master.cf.rpmnew
########################################### [100%]
Editing /etc/postfix/master.cf, adding missing entry for trace service
Editing /etc/postfix/master.cf, adding missing entry for verify service
 
    Note: the following files or directories still exist but are no
    longer part of Postfix:
 
     /etc/postfix/pcre_table /etc/postfix/regexp_table
     /usr/share/man/man8/nqmgr.8.gz
[root@knomta fc2]# 

The note is wrong.
 
[root@knomta fc2]# ls -l /etc/postfix/pcre_table
/etc/postfix/regexp_table /usr/share/man/man8/nqmgr.8.gz
ls: /etc/postfix/pcre_table: No such file or directory
ls: /etc/postfix/regexp_table: No such file or directory
ls: /usr/share/man/man8/nqmgr.8.gz: No such file or directory
[root@knomta fc2]#
Comment 1 Thomas Woerner 2004-06-21 08:24:40 EDT
Fixed in rawhide in rpm postfix-2.1.1-3.1 or newer.

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