Bug 702192
Summary: | zanata version info produces AttributeError: | ||
---|---|---|---|
Product: | [Retired] Zanata | Reporter: | Kenichi Takemura <ktakemur> |
Component: | Component-PythonClient | Assignee: | James Ni <jni> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ding-Yi Chen <dchen> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 1.3-alpha-1 | CC: | ebaak, sflaniga, zanata-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-11-29 06:15:20 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
Kenichi Takemura
2011-05-05 01:55:59 UTC
Also happens on RHEL 6 with zanata-python-client-1.2.3-1.el6.noarch The reason for this issue is the server have changed the structure of 'Version', there is no 'version name' and 'version description' any more. If you use 'zanata version info' on translate.jboss.org which running 1.2 version of zanata: "zanata version info --url=https://translate.jboss.org", the client works well and give correct info. So i think i will modify the zanata version info to make it compatible with all the version of zanata server. And it is better not use version info command on new server with zanata client 1.2.3. Best Regards Hi Kenichi, I build a new package 1.2.4 to fix this issue, you can find it on https://admin.fedoraproject.org/updates/zanata-python-client-1.2.4-1.fc14?_csrf_token=f6ade6ebe68d25c4ed193e01f216913458eae029 I also build the new package for other platforms If you test and prove that version 1.2.4 fix that issue, could you help to mark a stable Karma? Thanks Best Regards Verified and the package got Karma-ed.. I am curious... didn't we need fedora bug for this problem? |