Bug 658921
Summary: | setup should run newaliases in post | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Orion Poplawski <orion> |
Component: | setup | Assignee: | Ondrej Vasik <ovasik> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 14 | CC: | ovasik, pknirsch |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-12-03 15:42:59 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Orion Poplawski
2010-12-01 16:08:08 UTC
Strange... because /etc/aliases was not updated and is marked %config(noreplace) ... It's a bit more difficult to run /usr/bin/newaliases in setup %post, as you don't have bash in the case of setup installation - and due to dependencies only lua scriptlets can be used in setup. So during installation this /usr/bin/newaliases will be not run anyway and in the case of setup package update, there is no added content to /etc/newaliases - it was probably modified by user or another package. In other words - if user or other application modifies the default /etc/aliases, these are responsible for running newaliases (as recommended in default /etc/aliases) or restarting mailserver. I tend to close this NOTABUG. I sympathize with the issues, but what triggered the sendmail complaint is the timestamp of the file, which did change. If this can't be dealt with, I think CANTFIX is the appropriate resolution. But can't you test if /usr/bin/newaliases is present and run if it is? Can lua not execute binaries? It's a binary, not a shell script. Of course, it can be handled by lua script ( if posix.access("/usr/bin/newaliases", "x") then os.execute('/usr/bin/newaliases') end ). It should be harmless, but in most cases it is useless (as the update of setup should not change the /etc/aliases file)... I really don't know why the timestamp changed - as the file itself was not changed for quite a long ... maybe I have some timepreserving issue in setup package. I'll check this... Damned, you are right - git-archive - which is used for building tarballs - throws away timestamps. Ok, I'll run newaliases lua scriptlet part in future until I'll fix the timestamp preserving. Closing this RAWHIDE, if there will be future setup F-14 update, I'll include it there as well. |