On 19/10/2016 07:14, Kevin Simmons wrote: > In general, I could use a mentor I can ask questions of and get answers > from. I have been a tinkerer/user only of Gentoo in the past and am now > wanting to be more involved.
Sounds great! :) Not sure if I'd call myself a mentor, but feel free to send questions my way. > For instance, there is a bug to have > gramps-4.2.4 stable (it is ~amd64 ~x86 now). That's <https://bugs.gentoo.org/show_bug.cgi?id=597258>, right? The usual procedure is to CC arches on the bug - amd64@ and x86@ in that case. > To stabilize this package for amd64 and x86 it would also need to be > verified on x86. I suppose I could do that myself by creating an x86 > virtual guest and testing or I should ask for assistance via a bug to > x86@. x86@ would probably be slow to respond, and it's really a dying arch. A more lightweight solution in case you need it would be a chroot. > Also, when I run 'repoman full' from the proposed ebuild directory I get > QA issues for RDEPEND for dev-python/pyicu, which is also ~amd64. This > dependent package (and its dependencies) would need to be stable as > well. Ah, yes - I suggest opening stabilization bugs for these packages, and marking them us blocking gramps stabilization bug. > When it comes time to commit (repoman commit), do I need any user access > set up before I commit? repoman commit will create a local commit in your local git checkout. Only developers can push directly to Gentoo git. Otherwise you can maybe create a PR on github or just send a git-formatted patch for someone to proxy commit. Paweł
signature.asc
Description: OpenPGP digital signature
