From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RnWR2-0005BV-LJ for garchives@archives.gentoo.org; Wed, 18 Jan 2012 14:24:20 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 58599E067D; Wed, 18 Jan 2012 14:24:05 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id D17B3E060C for ; Wed, 18 Jan 2012 14:23:32 +0000 (UTC) Received: from devil (localhost [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ago) by smtp.gentoo.org (Postfix) with ESMTPSA id 211D91B4013 for ; Wed, 18 Jan 2012 14:23:32 +0000 (UTC) From: Agostino Sarubbo To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] How help in arch testing work Date: Wed, 18 Jan 2012 15:23 +0100 Message-ID: <4228441.jrAjLjLIeT@devil> User-Agent: KMail/4.7.4 (Linux/2.6.39-gentoo ; KDE/4.7.4; i686; ; ) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2225263.6KeTS7FRWv"; micalg="pgp-sha512"; protocol="application/pgp-signature" Content-Transfer-Encoding: 7Bit X-Archives-Salt: 0b7a11ae-606f-41fb-be03-d317ae6845e2 X-Archives-Hash: a57b00691c645cb4d8fb6f7a0acdc337 --nextPart2225263.6KeTS7FRWv Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" 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 --nextPart2225263.6KeTS7FRWv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQEcBAABCgAGBQJPFtXEAAoJEOTDgjZ80txd9isH/RPPAP8VrV52tyEEpMUaAkhv OWgp9rUaho5MeVacTcRoBILGSw5wqJg48oGOrUtNYy7rwz/JL5Ml2cphtI1nbljb OyiJKMf+4+HqoWUqT4J2ZtAvXEWHjCsPBh0EkpeV/auNDZSnm0n2RzBl3sg2NAff MuIws3xReuVSBZo3OnQYS3kzQdf94QCVIjpT7yzhpWOnQGGpXKTPANP/NDsfVfOF pbrNPVu4euMuBf9q54wqBV7skViEvF+0ChyQxRvWYL8o94Rrm5UIHCmvFDcRAZZo cYGjY12FeTVFp2pyHwB0dCWwbgsLRBKSjOZ4qoClnEMizKz8sPDDoxz+U8736XI= =Q8L4 -----END PGP SIGNATURE----- --nextPart2225263.6KeTS7FRWv--