Latest (enchancement) release. DIST OOoFBTools-2.40.zip 4836607 SHA256 de912d6641625197a941608f321ac800bcd101e552d9185ee9786be28ee80d2b SHA512 f0e95c31d1f4b463cfd84cfd0425b5beb8fdbb46018c5ef88d7093cd007d6146c36ec626195b9020d603be641b32803dab89906cd6daa28619c4fc2e219f0934 WHIRLPOOL e6c69afd40c447e160fa84a5e5f4aa8852254a9c0da03bc68cbae6eb3ed021865f2ee6d725cc87c476fc06f672d07b4d09c04dcb1c9bcd3b9e66e9de8429e869 Ebuild is the same with 2.39.
Not fixed. 2016-01-13 was released =app-officeext/ooofbtools-2.41 DIST OOoFBTools-2.41.zip 4837181 SHA256 5da7ffc60d4c2e747ddda98483147893613be0e4d9f1b220bf1f42bb7756060d SHA512 6879efb44530c017b119304922c8295847276abb7d939ef63ac3e541c9d58cb5c7799beb57c5e4ee2ae8bc5577d60456dfca947ba841a0eea71ea5b73a779a0c WHIRLPOOL 7c61afa7bd4798f204676dc1c54d0c1f8267533c5e99c684f27a5fa305c146adb5d132fc9abce7b72316d08d17c121eff018aa3e828c29e9740c852ecc4a4c71
The source has a file OOoFBTools_Help.pdf. Can you please add IUSE doc and add code to install this help file to the usual location with use of use doc. Otherwise, omly point I can find is DESCRIPTION too long by about 10 chars. The text within " " ought be <= 80 chars.
(In reply to Ian Delaney from comment #2) > The source has a file OOoFBTools_Help.pdf. > Can you please add IUSE doc and add code to install this help file to the > usual location with use of use doc. Otherwise, omly point I can find is > DESCRIPTION too long by about 10 chars. The text within " " ought be <= 80 > chars. I can do so, but. This is Russian-only document, it has no corresponding English version. And AFAIK Gentoo policy, installed docs _must_ provide English version. This (question about 'doc' use) was descussed in about 2.25 version bump.
(In reply to Ian Delaney from comment #2) > The source has a file OOoFBTools_Help.pdf. OOoFBTools_Help.pdf is not the only extra doc of this package. It also contains two example files. But: https://bugs.gentoo.org/show_bug.cgi?id=492654#c3 > …We do not install localized docs that do not have english counterpart. So, I install them with the following function: /etc/portage/env/app-officeext/ooofbtools: post_src_install() { dodoc OOoFBTools_Help.pdf docinto examples dodoc ExportToFB21_example-*.odt } Also it may be reasonable to install /usr/share/doc/ooofbtools-2.41/ChangeLog_Rus.txt.bz2 only for LINGUAS="ru".
You have all the info and options. Make a best decison with what you have that will be fine.
(In reply to Ian Delaney from comment #5) > You have all the info and options. Make a best decison with what you have > that will be fine. For now we should do just a version bump. Extra docs are skipped due to policy-incompatibility (both quoted manual and examples are Russian-only). About examples I'll think. Maybe in future versions sould be some improvements.
Not fixed. Next release. DIST OOoFBTools-2.42.zip 4837516 SHA256 c31a73a862734395a4c6ad45e3ff5aa36d0ec5acfd26d6d3e1c27de4ce7c24fc SHA512 a6945dd003c1b6a5be77c224e47d7b30b54ce28ea4a1aeada71ed401a0a6e9afacc08394da908d1f2765e8f4766e55479ed51a98067829bde950732ab27df302 WHIRLPOOL 5f9744331dd0d269b3ac1b6cce29316b7623fe719bd2d685ca75d2a021930d1fdd6c2b657597b69ead86814372da3f74ff342a19f2d0803e2af3acce93c9f872
(In reply to Sergey S. Starikoff from comment #7) > Not fixed. Next release. > ]I get the impression no-one has ever taught you how to make a submission in an attachment to execute a commit of the bumped version. To begin with; "Not fixed. Next release" I do not understand what you are trying to convey. Whatever form of bump or fix you are suggesting need be made into a unified diff that a developer can generate an ebuild ready to add to portage. How you were added as <maintainer type="person"> in the metadata was clearly done long ago and had no involvement with the current membership of the proxy-maint project. In short, textual prompts are merely textual prompts and do not lead to the package app-officeext/ooofbtools being wither fixed or bumped. If you wish for further support, it is available. See https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers
DESCRIPTION.toolong 3 app-officeext/ooofbtools/ooofbtools-2.38.ebuild: DESCRIPTION is 84 characters (max 80) app-officeext/ooofbtools/ooofbtools-2.39.ebuild: DESCRIPTION is 84 characters (max 80) app-officeext/ooofbtools/ooofbtools-2.42.ebuild: DESCRIPTION is 84 characters (max 80) Hello, Can you please shorter the ebuild description? Thanks. Amy
author Amy Winston <amynka@gentoo.org> 2016-02-22 06:47:41 (GMT) committer Amy Winston <amynka@gentoo.org> 2016-02-22 06:48:50 (GMT) commit 16b792d66a3f3b276070eab526da82270cc12f2c app-officeext/ooofbtools: 2.42 version bump bug #567520 Please add to the comments to this bug the shortened description. Thanks. Amy
(In reply to Amy Winston from comment #10) > Please add to the comments to this bug the shortened description. Thank you! Are there any conventions or recommendations about Description string length? Excuse me my English. As shorter variant I can suggest something like: «Text processing tool with FictionBook2 convertor and validator»
(In reply to Sergey S. Starikoff from comment #11) > (In reply to Amy Winston from comment #10) > > Please add to the comments to this bug the shortened description. > > Thank you! > > Are there any conventions or recommendations about Description string length? > > Excuse me my English. As shorter variant I can suggest something like: > «Text processing tool with FictionBook2 convertor and validator» What about this? "OpenOffice extension for the FictionBook2 format with validation" Acceptable?
The aim here was to have Sergey make and submit a patch in a unified diff within this bug to generate a bumped ooofbtools-2.42.ebuild. That's all. You had all the pieces at your disposal, you just needed to put them together and make a diff style patch. In this case, it has all been done for you. Simply take note for you next big fix / bump
(In reply to Ian Delaney from comment #13) > The aim here was to have Sergey make and submit a patch in a unified diff > within this bug to generate a bumped ooofbtools-2.42.ebuild. That's all. You You are wrong. The aim is to fix the tree for the users and if there is a single dev taking care with the little information Sergey brought up, everything is all right.
you are making policy on the fly jlec. I am in fact keeping true to how hwoarang made and ran this project. You have neither place nor right to declare me wrong. Do no do this again
(In reply to Ian Delaney from comment #15) > you are making policy on the fly jlec. I am in fact keeping true to how > hwoarang made and ran this project. You have neither place nor right to > declare me wrong. > Do no do this again I hope you just have a bad day. Be very, very careful to not overstep the thin line you have already drawn in front of you.
