Bug 146733
| Summary: | system-config-bind %postinstall ends with %doc ?!? | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> |
| Component: | system-config-bind | Assignee: | Jason Vas Dias <jvdias> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | h1k6zn2m, jorton |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 4.0.0-4 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-04-27 12:34:19 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 136450 | ||
|
Description
Alexandre Oliva
2005-02-01 02:48:16 UTC
Yes, I know - a missing new line. This problem has no effect on system-config-bind's functionality or operation - it still works fine with this problem. This will be fixed in the next version: system-config-bind-4.0.0-4, which I will be releasing by Friday (2005-02-04). This bug is still present in the Raw Hide package. Installing system-config-bind-4.0.0-3.noarch. /var/tmp/rpm-tmp.43199: line 11: fg: no job control error: %post(system-config-bind-4.0.0-3.noarch) scriptlet failed, exit status 1 Any news on this one? system-config-bind-4.0.0-3 is still the latest on rawhide, and it still has the problem. I'm hoping to get time to finish off system-config-bind this week, with support for all the 'todo' record types & options (mainly dnssec stuff), the html manual, and the fix for this bug. Can it wait til then ? Both installation and upgrade do leave a working system-config-bind in place. *** Bug 150011 has been marked as a duplicate of this bug. *** This bug was fixed in version 4.0.0-4 |