Bug 139069
| Summary: | Incorrect file reference in dhcpv6 description | ||
|---|---|---|---|
| Product: | [Fedora] Fedora Localization | Reporter: | Göran Uddeborg <goeran> |
| Component: | Other language | Assignee: | Dimitris Glezos <dimitris> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | A S Alam <aalam> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | mattdm, menthos, mshao, trans |
| Target Milestone: | --- | Keywords: | EasyFix |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-09-21 16:55:12 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
Göran Uddeborg
2004-11-12 19:45:25 UTC
Ah, forgot to say: the same bug is there in dhcpv6_client too. Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you! In FC5 this is fixed in dhcpv6 but remains in dhcpv6_client. moving to FC5 as per comment #3. Thanks. reassignn to me It seems that current sv.po does not contain /usr/share/dhcpv6* in any of the descriptions, it's always /usr/share/doc/dhcpv6*. So from this point of view the bug is fixed. But there seem to be some buggy translations where the translation contains "/usr/share/doc/dhcpv6" even though the original string doesn't. This is why I'm trying to toss this bug to "Fedora Localization" product. Stepan, can you please send an email to fedora-trans-list with more information on how people can fix this (if it does need fixing from our tranlators and they indeed can fix it)? I think I'm not the best asignee for this bug. The description for 1.0.14-1.fc9 doesn't have this problem any more. |