From: Agostino Sarubbo <ago@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] How help in arch testing work
Date: Wed, 18 Jan 2012 15:23 +0100 [thread overview]
Message-ID: <4228441.jrAjLjLIeT@devil> (raw)
[-- Attachment #1: Type: text/plain, Size: 3238 bytes --]
This mail is come from my long time experience about testing.
So, everytime, I must suggest the same things and I can say that at some point
it gets boring.
I appreciate the work of all, but I must say that some people pay little
attention to stablereq bugs, so this mail wants to be a short reminder of what
could decrease our work.
1) There is a discussion[1] about it, but for the moment, a stablereq should
be "keywording and stabilization" and enhancement importance.
If you need to accelerate the stabilization please set high and not from
enhancement to critical and so on.
Don't forget STABLEREQ keyword or the bug will not appears in our list.
2) _Before_ filing a request, please run repoman full, to be sure that there
is nothing to fix, then take a look at the ebuild and make sure your ebuild
have a minimum of QA; all external binary called in the ebuild(sed, mv, cp,
ln, rm, and so on) should have 'die'; if you don't use EAPI4, make sure that
all portage helper[2] have also '|| die'.
3) Check your rdepend, where is possible with scanelf[3] and if you declare
it, please, as you said, exclude gcc/glibc and all package from @system
4) Nobody knows how work all packages in tree, so there are obvious packages
like a browsers, IM, audio player,that is easy decide if is ok or not, but
there are also packages that an Arch tester has never seen, so is a lack of
time everytime google about it or ask to maintainer, so, please specify what
test you want for this package; e.g.
-only compile test
-compile test and make sure src_test goes well
-make sure /usr/bin/${foo} works properly in ${that} manner
-see 5) about library
So, you can write one time 'how to' and copy/paste for the future stablereq; I
guess I'm not asking a long and difficult task.
5) If is a library, obviously, we can try to rebuild stable RDEPENDS in tree
and an easy way to check the list of rdepend is asking our bot:
!rdep ${package}
Unfortunately it prints a complete list of RDEPEND(stable+testing), and is a
lack of time checking manually what is the list of stable packages.
So you can lighten our work in 2 ways:
a) Please rebuild the following list of rdepends.( if no need to rebuild all
because maintainer already do it)
b) Please rebuild all rdepends.
So, unfortunately, I don't know a rapid way to have only a stable list of
packages, so if really there isn't it, is very very appreciated print the list
of packages that needs rebuild
Sorry in advance if there is and I'm ignoring it, please tell me.
I want to point out that this is not a polemic, but is a way to suggest what
you can do for arch teams to increase the quality of teamwork and do not waste
precious time.
[1]: https://bugs.gentoo.org/show_bug.cgi?id=381627
[2]: qlist -e portage | grep ebuild-helpers
[3]: amd64box ~ # cat /usr/local/bin/scan
#!/bin/bash
qlist -e "$@" | xargs scanelf -L -n -q -F '%n #F' | tr , ' ' | xargs qfile -Cv
| sort -u | awk '{print $1}' | uniq
--
Agostino Sarubbo ago -at- gentoo.org
Gentoo/AMD64 Arch Security Liaison
GPG: 0x7CD2DC5D
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2012-01-18 14:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 14:23 Agostino Sarubbo [this message]
2012-01-18 14:42 ` [gentoo-dev] How help in arch testing work Tobias Klausmann
2012-01-18 14:55 ` Alexis Ballier
2012-01-18 15:44 ` Rich Freeman
2012-01-18 16:45 ` Mike Frysinger
2012-01-18 18:42 ` Rich Freeman
2012-01-18 20:01 ` Mike Frysinger
2012-01-18 20:45 ` Rich Freeman
2012-01-19 2:23 ` [gentoo-dev] " Duncan
2012-01-19 16:46 ` Mike Frysinger
2012-01-20 0:12 ` Duncan
2012-01-19 3:05 ` [gentoo-dev] " Mike Frysinger
2012-01-19 3:41 ` Mike Gilbert
2012-01-19 16:42 ` Ian Stakenvicius
2012-01-19 17:05 ` Mike Frysinger
2012-01-19 14:04 ` Rich Freeman
2012-01-19 17:02 ` Mike Frysinger
2012-01-18 22:26 ` Agostino Sarubbo
2012-01-21 20:23 ` [gentoo-dev] " Christian Faulhammer
2012-01-18 15:05 ` [gentoo-dev] " Mike Frysinger
2012-01-18 15:48 ` Donnie Berkholz
2012-01-18 17:32 ` "Paweł Hajdan, Jr."
2012-01-18 18:10 ` Mike Frysinger
2012-01-18 18:15 ` "Paweł Hajdan, Jr."
2012-01-18 19:02 ` Markos Chandras
2012-01-18 20:02 ` Mike Frysinger
2012-01-19 8:56 ` [gentoo-dev] " Michael
2012-01-27 9:41 ` [gentoo-dev] " Thomas Kahle
2012-01-27 9:47 ` "Paweł Hajdan, Jr."
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4228441.jrAjLjLIeT@devil \
--to=ago@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox