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