1 |
This mail is come from my long time experience about testing. |
2 |
|
3 |
So, everytime, I must suggest the same things and I can say that at some point |
4 |
it gets boring. |
5 |
|
6 |
I appreciate the work of all, but I must say that some people pay little |
7 |
attention to stablereq bugs, so this mail wants to be a short reminder of what |
8 |
could decrease our work. |
9 |
|
10 |
1) There is a discussion[1] about it, but for the moment, a stablereq should |
11 |
be "keywording and stabilization" and enhancement importance. |
12 |
If you need to accelerate the stabilization please set high and not from |
13 |
enhancement to critical and so on. |
14 |
Don't forget STABLEREQ keyword or the bug will not appears in our list. |
15 |
|
16 |
2) _Before_ filing a request, please run repoman full, to be sure that there |
17 |
is nothing to fix, then take a look at the ebuild and make sure your ebuild |
18 |
have a minimum of QA; all external binary called in the ebuild(sed, mv, cp, |
19 |
ln, rm, and so on) should have 'die'; if you don't use EAPI4, make sure that |
20 |
all portage helper[2] have also '|| die'. |
21 |
|
22 |
3) Check your rdepend, where is possible with scanelf[3] and if you declare |
23 |
it, please, as you said, exclude gcc/glibc and all package from @system |
24 |
|
25 |
4) Nobody knows how work all packages in tree, so there are obvious packages |
26 |
like a browsers, IM, audio player,that is easy decide if is ok or not, but |
27 |
there are also packages that an Arch tester has never seen, so is a lack of |
28 |
time everytime google about it or ask to maintainer, so, please specify what |
29 |
test you want for this package; e.g. |
30 |
-only compile test |
31 |
-compile test and make sure src_test goes well |
32 |
-make sure /usr/bin/${foo} works properly in ${that} manner |
33 |
-see 5) about library |
34 |
|
35 |
So, you can write one time 'how to' and copy/paste for the future stablereq; I |
36 |
guess I'm not asking a long and difficult task. |
37 |
|
38 |
5) If is a library, obviously, we can try to rebuild stable RDEPENDS in tree |
39 |
and an easy way to check the list of rdepend is asking our bot: |
40 |
!rdep ${package} |
41 |
Unfortunately it prints a complete list of RDEPEND(stable+testing), and is a |
42 |
lack of time checking manually what is the list of stable packages. |
43 |
So you can lighten our work in 2 ways: |
44 |
a) Please rebuild the following list of rdepends.( if no need to rebuild all |
45 |
because maintainer already do it) |
46 |
b) Please rebuild all rdepends. |
47 |
So, unfortunately, I don't know a rapid way to have only a stable list of |
48 |
packages, so if really there isn't it, is very very appreciated print the list |
49 |
of packages that needs rebuild |
50 |
Sorry in advance if there is and I'm ignoring it, please tell me. |
51 |
|
52 |
|
53 |
|
54 |
I want to point out that this is not a polemic, but is a way to suggest what |
55 |
you can do for arch teams to increase the quality of teamwork and do not waste |
56 |
precious time. |
57 |
|
58 |
|
59 |
[1]: https://bugs.gentoo.org/show_bug.cgi?id=381627 |
60 |
[2]: qlist -e portage | grep ebuild-helpers |
61 |
[3]: amd64box ~ # cat /usr/local/bin/scan |
62 |
#!/bin/bash |
63 |
qlist -e "$@" | xargs scanelf -L -n -q -F '%n #F' | tr , ' ' | xargs qfile -Cv |
64 |
| sort -u | awk '{print $1}' | uniq |
65 |
|
66 |
-- |
67 |
Agostino Sarubbo ago -at- gentoo.org |
68 |
Gentoo/AMD64 Arch Security Liaison |
69 |
GPG: 0x7CD2DC5D |