Bug 573100
| Summary: | update wqy-bitmap-fonts to the new upstream release 1.0.0-RC1 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Qianqian Fang <fangqq> |
| Component: | wqy-bitmap-fonts | Assignee: | Qianqian Fang <fangqq> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | fangqq, fonts-bugs, i18n-bugs, mtasaka, petersen |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | wqy-bitmap-fonts-1.0.0-0.1.rc1.fc11 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-03-14 13:36:30 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
Qianqian Fang
2010-03-12 20:36:46 UTC
wqy-bitmap-fonts-1.0.rc1-0.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/wqy-bitmap-fonts-1.0.rc1-0.fc12 wqy-bitmap-fonts-1.0.rc1-0.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/wqy-bitmap-fonts-1.0.rc1-0.fc11 wqy-bitmap-fonts-1.0.rc1-0.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/wqy-bitmap-fonts-1.0.rc1-0.fc13 EVR (Epoch-Version-Release) must be "1.0-0.X.rc1" (where X is some integer), otherwise when 1.0 is released, upgrade path cannot correctly be kept because rpm thinks "1.0rc1 > 1.0". Also it seems that the correct version seems "1.0.0", not "1.0" wqy-bitmap-fonts-1.0.0-0.1.rc1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/wqy-bitmap-fonts-1.0.0-0.1.rc1.fc12 wqy-bitmap-fonts-1.0.0-0.1.rc1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/wqy-bitmap-fonts-1.0.0-0.1.rc1.fc11 wqy-bitmap-fonts-1.0.0-0.1.rc1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/wqy-bitmap-fonts-1.0.0-0.1.rc1.fc13 (In reply to comment #4) > EVR (Epoch-Version-Release) must be "1.0-0.X.rc1" (where X is > some integer), otherwise when 1.0 is released, upgrade path > cannot correctly be kept because rpm thinks "1.0rc1 > 1.0". > > Also it seems that the correct version seems "1.0.0", not "1.0" Thanks for pointing this out. The issue is now corrected. The new EVR looks like 1.0.0-0.1.rc1. Updates for F11~F13 were submitted. Thank you for quick update. New pkgs seems correctly versioned. Now would you - untag wqy-bitmap-fonts-1.0.rc1-0.fc14 on koji (i.e. $ koji untag-pkg dist-f14 wqy-bitmap-fonts-1.0.rc1-0.fc14 ) - Revoke bodhi submittion for 1.0.rc1-0.fcYYYY to make it sure that anything unexpected won't happen during push process? (In reply to comment #9) > Thank you for quick update. New pkgs seems correctly versioned. > > Now would you > - untag wqy-bitmap-fonts-1.0.rc1-0.fc14 on koji > (i.e. $ koji untag-pkg dist-f14 wqy-bitmap-fonts-1.0.rc1-0.fc14 ) done > - Revoke bodhi submittion for 1.0.rc1-0.fcYYYY done > > to make it sure that anything unexpected won't happen during push > process? let me know if there is anything else for getting the update through. thanks by the way, shall I untag F11~F13 too? (In reply to comment #11) > by the way, shall I untag F11~F13 too? Not strictly needed. F-14 is special because all pkgs rebuilt for F-14 (devel) will be automatically pushed into repository. wqy-bitmap-fonts-1.0.0-0.1.rc1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. wqy-bitmap-fonts-1.0.0-0.1.rc1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. wqy-bitmap-fonts-1.0.0-0.1.rc1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. |