Please keyword dev-perl/DateTime-Format-SQLite for ~ppc and ~arm
1. Do you have either of these arches? 2. Is this the result of some package you also wish to use needing this one with keywording? 3. Can you personally elide the keywords and attach a full build _and_ test log demonstrating it works on all the arches you're requesting a keywording for? Feel free to reopen this bug once these questions are answered. ( You don't *have* to satisfy all these requirements, but clarity of information and personal attestation that "it works" and "its dependencies work" will greatly accelerate our adding of keywords )
*** Bug 719140 has been marked as a duplicate of this bug. ***
I closed bug 719140 and added keyword request for dev-perl/LWP-UserAgent-Determined to this bug. dev-perl/LWP-UserAgent-Determined only needs ~arm as it already has ~ppc. Both are required by new grabber tv_grab_zz_sdjson_sqlite (In reply to Kent Fredric (IRC: kent\n) from comment #1) > 1. Do you have either of these arches? No. > 2. Is this the result of some package you also wish to use needing this one > with keywording? Yes. I am doing a version bump to media-tv/xmltv-0.6.1. A new perl grabber script tv_grab_zz_sdjson_sqlite requires these 2 perl modules. The current version xmltv-0.5.70 supports ~arm and ~ppc. > 3. Can you personally elide the keywords and attach a full build _and_ test > log demonstrating it works on all the arches you're requesting a keywording > for? No. See PR media-tv/xmltv: Bump version 0.6.1 #15275 media-tv/xmltv/xmltv-0.6.1.ebuild fails repoman ci unless KEYWORDS ~arm and ~ppc are removed as they are in PR #15275. This emerges without error for ~amd64. emerge with USE="zz-sdjson-sqlite" in order to actually install the perl script that uses these modules.
(In reply to Wilson M. Michaels from comment #3) > I am doing a version bump to media-tv/xmltv-0.6.1. A new perl grabber script > tv_grab_zz_sdjson_sqlite requires these 2 perl modules. The current version > xmltv-0.5.70 supports ~arm and ~ppc. > Awesome :). Knowing the /why/ in this case helps a heap. However, there is generally "an approach" that I use myself in this situation. 1. In doing the bump, I drop the keywords. 2. Then, after the package is in tree, I file a keywording request, _for my own package_, including the new deps. That way anyone who looks at the tree will see "Old version has this, new version does not", and that alone serves as good grounds for keywording. It also means you can focus on getting the job done first and foremost, and then worrying about keywording later. It also means that once a package is keyworded to satisfy the dependency, nobody winds up asking "why is this keyworded? Nothing depends on this with those keywords". But you can happily keep this req open regardless of whether you decide to take my approach. Just don't let waiting for arches stop you doing something useful here if you don't have to.
~ppc keyworded
~arm added, closing
