Bug 1094015
Summary: | Review Request: cwtex-q-fonts - a series of modern traditional Chinese fonts | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Cheng-Chia Tseng <pswo10680> |
Component: | Package Review | Assignee: | Nobody's working on this, feel free to take it <nobody> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | fonts-bugs, i18n-bugs, i, lantw44, msuchy, package-review, pswo10680, zebob.m |
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: | 2020-07-21 03:21:18 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: | 177841 |
Description
Cheng-Chia Tseng
2014-05-04 11:14:27 UTC
Here are my koji build task urls: f20 http://koji.fedoraproject.org/koji/taskinfo?taskID=6811265 f21 http://koji.fedoraproject.org/koji/taskinfo?taskID=6811286 Let me see if I can find some time here but before that I see you need sponsorship. Have you started reviewing other new packages? If yes please provide here links to your package reviews. If you are not knowing about sponsorship process then please have a look at https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group Look for new packages at http://fedoraproject.org/PackageReviewStatus/NEW.html you may also find following links interested to read http://fedoraproject.org/wiki/Using_Fedora_GIT http://fedoraproject.org/wiki/Packaging_tricks http://fedoraproject.org/wiki/How_to_create_an_RPM_package http://fedoraproject.org/wiki/Packaging:ReviewGuidelines http://fedoraproject.org/wiki/Package_Review_Process Thank you for your informaiton about sponsorship process! :) I haven't read that before, and haven't started reviewing other new packages yet. However, I will follow those instructions to get well prepared! rpmlint on source and binary rpms gave cwtex-q-fangsong-fonts.noarch: W: wrong-file-end-of-line-encoding /usr/share/doc/cwtex-q-fangsong-fonts/license.txt cwtex-q-fonts.src:37: W: macro-in-comment %package cwtex-q-fonts.src:41: W: macro-in-comment %description cwtex-q-fonts.src:42: W: macro-in-comment %common_desc cwtex-q-fonts.src:44: W: macro-in-comment %{name} cwtex-q-fonts.src:50: W: macro-in-comment %{name} cwtex-q-fonts.src:50: W: macro-in-comment %{version} cwtex-q-fonts.src:50: W: macro-in-comment %{release} cwtex-q-fonts.src:64: W: macro-in-comment %{name} cwtex-q-fonts.src:64: W: macro-in-comment %{version} cwtex-q-fonts.src:64: W: macro-in-comment %{release} cwtex-q-fonts.src:78: W: macro-in-comment %{name} cwtex-q-fonts.src:78: W: macro-in-comment %{version} cwtex-q-fonts.src:78: W: macro-in-comment %{release} cwtex-q-fonts.src:92: W: macro-in-comment %{name} cwtex-q-fonts.src:92: W: macro-in-comment %{version} cwtex-q-fonts.src:92: W: macro-in-comment %{release} cwtex-q-fonts.src:106: W: macro-in-comment %{name} cwtex-q-fonts.src:106: W: macro-in-comment %{version} cwtex-q-fonts.src:106: W: macro-in-comment %{release} cwtex-q-fonts.src:159: W: macro-in-comment %files cwtex-q-fonts.src:160: W: macro-in-comment %defattr cwtex-q-fonts.src:161: W: macro-in-comment %doc cwtex-q-fonts.src: W: invalid-url Source0: cwtex-q-fonts-v02-1.tar.xz cwtex-q-hei-fonts.noarch: W: wrong-file-end-of-line-encoding /usr/share/doc/cwtex-q-hei-fonts/license.txt cwtex-q-kai-fonts.noarch: W: wrong-file-end-of-line-encoding /usr/share/doc/cwtex-q-kai-fonts/license.txt cwtex-q-ming-fonts.noarch: W: wrong-file-end-of-line-encoding /usr/share/doc/cwtex-q-ming-fonts/license.txt cwtex-q-yuan-fonts.noarch: W: spelling-error %description -l en_US yaun -> yuan, yarn, faun cwtex-q-yuan-fonts.noarch: W: wrong-file-end-of-line-encoding /usr/share/doc/cwtex-q-yuan-fonts/license.txt 6 packages and 0 specfiles checked; 0 errors, 29 warnings. ==> Fix for above issues are as 1) when writing macros in comments always add extra % so %{name} should be %%{name} 2) wrong-file-end-of-line-encoding messages, fix this by using https://fedoraproject.org/wiki/PackageMaintainers/Common_Rpmlint_Issues#wrong-file-end-of-line-encoding 3) In the changelog you don't need dist tag i.e. change 0.2-1%{?dist} to 0.2-1 4) For fedora packaging only you don't need now a) removal of buildroot in %install b) %clean section See more about this https://fedoraproject.org/wiki/PackagingGuidelines#.25clean and https://fedoraproject.org/wiki/PackagingGuidelines#BuildRoot_tag I did not like the -common for just few (here 2) files which becomes one more dependent package for all other fonts subpackages. So, decide if you want to keep -common in your package then enable lines in comments else remove lines with comments. Note with every update to package you should increase release tag number by 1 and submit new package for further review. OK, I have corrected those issues you mentioned and re-uploaded to my fedorapeople space. Release tag number is updated too. Spec URL: http://zerng07.fedorapeople.org/SPECS/cwtex-q-fonts.spec SRPM URL: http://zerng07.fedorapeople.org/SRPMS/cwtex-q-fonts-0.2-2.fc20.src.rpm Thanks a lot! :) A quick look into given spec link issues 1, 2 fixed issue 3 fixed but you need to add changelog entry with every update and write lines there about what has changed from last release. For the new package you can add changelog like * Sat Jun 28 2014 Cheng-Chia Tseng <pswo10680> - 0.2-2 - fixed issues reported in package review issue 4, you have not replied whether you want this package only for Fedora or you also want this package in el6 or epel7 remove un-necessary comment lines OK, I finally figured it out. Changlog about this release is added. As issue 4, I would like to want this package included in epel6 or 7 too. Sorry that I don't understand the question well at first. :p The link of guidelines you provided at comment 4 mentioned that the %clean section is not required for F-13 and above. Each package for F-12 and below (or EPEL 5) MUST have a %clean section. So if I want it included in epel6 and above, I don't have to add those %clean section back right? Those un-necessary comment lines are all removed this time. :) Spec URL: http://zerng07.fedorapeople.org/SPECS/cwtex-q-fonts.spec SRPM URL: http://zerng07.fedorapeople.org/SRPMS/cwtex-q-fonts-0.2-2.fc20.src.rpm Thanks for your help! For EPEL packaging guidelines see http://fedoraproject.org/wiki/EPEL:Packaging OK. EPEL packaging guidelines says that %clean section is not required for epel6 or above. I got that. The SPEC should be fine now, am I right? same for removal of buildroot in %install in http://fedoraproject.org/wiki/EPEL:Packaging#Prepping_BuildRoot_For_.25install else spec looks good but I need to check fontconfig contents. Meanwhile you can start reviewing work of other packages for your sponsorship. Thanks! I will find some packages to review! :) Hi, Do you get time to review packages? Hi Parag, I was busy translating GNOME, Fedora and Blender for last few months and could not find much time to review packages. I will try to review some in the following weeks. Sorry for taking you so long. :P Thanks for the update on this review. We can wait. Any updates here? I find I don't have much time working on packaging in this period. :( The situation is that we, the community in Taiwan, don't have people working on packaging here. I would like to help with this, so I am translating and learning How to create an RPM package on wiki now to promote RPM packaging in these days. [1] I will apply for sponsoring in the future after my review some packages. Sorry for the long-time-delay. ;P [1] https://fedoraproject.org/wiki/How_to_create_an_RPM_package/zh-tw Thanks for quick reply. I will be happy to offer any kind of packaging help. Feel free to contact me on my email if you need any help. Thank you very much! :) I'm willing to help as well being as a Chinese ;) Cool! You guys are so kind! Ping. Any progress here? I'm sorry that I got a new job that taking about all of my time and even have to work on Saturday until noon. I have to admit that I rarely have time to do work on package reviews, so I won't apply for sponsoring in next 2 years. I am going to remove the FE-NEEDSPONSOR tag. However, I will update this package to catch up the new upstream version in next 2 weeks, and keep refreshing this font package. I think that is what I can do now in this period. Thanks for notifying me! :) Hi, I am working on 0.4 version today, and I will upload the spec and SRPM tomorrow. As for the sponsorship, I find I don't have much free time working on packaging after my new job since August. Maybe I will apply that after being used to my new job and having more free time. :P Spec URL: http://zerng07.fedorapeople.org/SPECS/cwtex-q-fonts.spec SRPM URL: http://zerng07.fedorapeople.org/SRPMS/cwtex-q-fonts-0.4-1.fc23.src.rpm This is an automatic check from review-stats script. This review request ticket hasn't been updated for some time. We're sorry it is taking so long. If you're still interested in packaging this software into Fedora repositories, please respond to this comment clearing the NEEDINFO flag. You may want to update the specfile and the src.rpm to the latest version available and to propose a review swap on Fedora devel mailing list to increase chances to have your package reviewed. If this is your first package and you need a sponsor, you may want to post some informal reviews. Read more at https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group. Without any reply, this request will shortly be considered abandoned and will be closed. Thank you for your patience. The fonts are not actively maintained, there is no new release since my 2015 package. And, I don't have time to maintain the package further. Plus, users can still install the fonts manually themselves. I decide to Close this bug report. Thanks! |