[gentoo-dev] finding reverse dependencies for arch testing (and other purposes)

[gentoo-dev] finding reverse dependencies for arch testing (and other purposes)

["Paweł Hajdan, Jr."]

[-- Attachment #1: Type: text/plain, Size: 906 bytes --]

I uploaded my script for finding reverse dependencies here:
http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=summary

Advantages over existing solutions (browsing to websites like tinderbox
or qa-reports):

- only prints stable packages when run on a stable system (no need to
manually filter out things)
- takes a list of packages as input, making it more effective for a
batch workflow (we're short on time, batching is often critical)
- produces output that can be fed to emerge after stripping comment
lines (no junk after package names); again this is for the batch workflow

It is still reasonably fast. On my machine it completes within 30 seconds.

Comments welcome. I'd be very happy to adapt this to your needs. My main
goal is to share those little scripts I use with others so we can all
become more productive (and have more time for other things).

Paweł


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]

Re: [gentoo-dev] finding reverse dependencies for arch testing (and other purposes)

[Markos Chandras]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 09/19/11 20:30, "Paweł Hajdan, Jr." wrote:
> I uploaded my script for finding reverse dependencies here: 
> http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=summary
>
>  Advantages over existing solutions (browsing to websites like
> tinderbox or qa-reports):
> 
> - only prints stable packages when run on a stable system (no need
> to manually filter out things) - takes a list of packages as input,
> making it more effective for a batch workflow (we're short on time,
> batching is often critical) - produces output that can be fed to
> emerge after stripping comment lines (no junk after package names);
> again this is for the batch workflow
> 
> It is still reasonably fast. On my machine it completes within 30
> seconds.
> 
> Comments welcome. I'd be very happy to adapt this to your needs. My
> main goal is to share those little scripts I use with others so we
> can all become more productive (and have more time for other
> things).
> 
> Paweł
> 

Maybe it is about time to gather all the arch-testing scripts we have
around, package them as a single tarball and create an ebuild for that?

- -- 
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iQIcBAEBCgAGBQJOd38FAAoJEPqDWhW0r/LCiIYQAJN5PJE0cF3TptFJWnCuRMKe
Ul3rWcBaH46GE0oZpeRyTNcnWZmNoNKEx+50OQ7vl7G0Q8Dtg5gvXRpxO7SrfKIj
JAspqX9RN3CO3Y5JRXL28SoJkPX3lLwX/FkejBARETRRKgZjJVOX3w5GOi/o7gm3
65NQ7W5EHp6j0ooGdsXucqVRQ2o8WbbRMHC0h2FR8SAC79pO/aEPh5OGkHOGcvLw
KSMKEaLsTucmyt+D5xh3bXQXR8e/xVTKzVEA3Yb8eic85CjglzxCDixnLA6EFWaX
bqcqyTPzbczZIF1yfyy8O8YfQdFlWH5OGxfu/kh7kBfkkjtJHubBJpoAdTvCHAot
GH7s1vMvITeCkpX6y9k1Cy0YLE/ebSM/iL4T7WnDQAy4nVApjI8k8770Gckr18NM
LCflW2aebKVT4QoWjgdxA3ABuisfqpPJhcpARjjzDTFcKeJQfySZRO5MFotIMgGK
ZTFeQOgpAupwjZswwtWQ19zqc6pDSa4u4RQZs5MZvB9eOWIwXs5xWLzZlqfOf6yv
7wILhX60FOxan+Qb/PU8+AnIytq4gqALGOnjExoe9M8Uk70vI6R4hokoxQJUrbxW
szG1jhq9gQQQTEQ5FGa7/erI//vLXIpdpdjwVCtp7j7CkRUmQH1sHATWoLhiUNOv
7VoMY3ocrF/+DOc7C0xP
=Vh0j
-----END PGP SIGNATURE-----

Re: [gentoo-dev] finding reverse dependencies for arch testing (and other purposes)

[Thomas Kahle]

[-- Attachment #1: Type: text/plain, Size: 1594 bytes --]

On 10:30 Mon 19 Sep 2011, "Paweł Hajdan, Jr." wrote:
> I uploaded my script for finding reverse dependencies here:
> http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=summary

app-portage/tatt does that for some time already.  It reads the list
from the tinderbox website and then uses eix to find stable rdeps.  It
also writes a script that builds the stable rdeps and reports back what
failed.

> Advantages over existing solutions (browsing to websites like tinderbox
> or qa-reports):
> 
> - only prints stable packages when run on a stable system (no need to
> manually filter out things)
> - takes a list of packages as input, making it more effective for a
> batch workflow (we're short on time, batching is often critical)
> - produces output that can be fed to emerge after stripping comment
> lines (no junk after package names); again this is for the batch workflow

tatt can do all this.

> It is still reasonably fast. On my machine it completes within 30 seconds.

> Comments welcome. I'd be very happy to adapt this to your needs. My main
> goal is to share those little scripts I use with others so we can all
> become more productive (and have more time for other things).

I'm currently working on a new version of tatt which includes Pawel's
fantastic ncurses bug-browser.  Code is in the bugbrowser branch of
https://github.com/tom111/tatt, but I'm still working on it.

I highly welcome Pawel's tools and will shamelessly immitate it's best
features.

Cheers,
Thomas



-- 
Thomas Kahle
http://dev.gentoo.org/~tomka/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

Re: [gentoo-dev] finding reverse dependencies for arch testing (and other purposes)

[Thomas Kahle]

[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]

Hi!

On 20:42 Mon 19 Sep 2011, Markos Chandras wrote:
> On 09/19/11 20:30, "Paweł Hajdan, Jr." wrote:
> > I uploaded my script for finding reverse dependencies here: 
> > http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=summary
> >
> >  Advantages over existing solutions (browsing to websites like
> > tinderbox or qa-reports):
> > 
> > - only prints stable packages when run on a stable system (no need
> > to manually filter out things) - takes a list of packages as input,
> > making it more effective for a batch workflow (we're short on time,
> > batching is often critical) - produces output that can be fed to
> > emerge after stripping comment lines (no junk after package names);
> > again this is for the batch workflow
> > 
> > It is still reasonably fast. On my machine it completes within 30
> > seconds.
> > 
> > Comments welcome. I'd be very happy to adapt this to your needs. My
> > main goal is to share those little scripts I use with others so we
> > can all become more productive (and have more time for other
> > things).
> > 
> > Paweł
> > 
> 
> Maybe it is about time to gather all the arch-testing scripts we have
> around, package them as a single tarball and create an ebuild for that?

For me personally I'm gathering all functionality inside tatt which aims
at doing it all from one executable.  Some x86 arch testers use it
already, but I must admit that development has been slow.  

People (including me) seem to find it hard to start using somebody elses
tools.  There was app-portage/gatt which I tried out when I became an
arch tester, but I found it insanely complicated, so I wrote tatt.  I
assume that at some point people will find tatt too complicated and
write yaatt (yet another ... ).  In principle, this is what Pawel is
doing.  I think an ecosystem of different arch testing tools is really
useful.

Let's have a page in our docs where everybody can explain his or her
tool.  Where in the hierarchy should the page be?  How about:
http://www.gentoo.org/proj/en/base/arch-testing

Cheers,
Thomas


-- 
Thomas Kahle
http://dev.gentoo.org/~tomka/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

Re: [gentoo-dev] finding reverse dependencies for arch testing (and other purposes)

[Rich Freeman]

On Wed, Sep 21, 2011 at 12:34 PM, Thomas Kahle <tomka@gentoo.org> wrote:
> Let's have a page in our docs where everybody can explain his or her
> tool.  Where in the hierarchy should the page be?  How about:
> http://www.gentoo.org/proj/en/base/arch-testing

Please!  And the documentation should include examples of common
workflows, not just a dump of command line options and what they do.

Let's start with the use case of I have a stablereq for a package and
I want to test it.  Just tell me how to do it, and don't make me
figure out which combination of options works best.  Oh, and make sure
the instructions include any necessary cleanup if the process leaves
cruft in package.keywords/etc.

Rich

Re: [gentoo-dev] finding reverse dependencies for arch testing (and other purposes)

[Markos Chandras]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 09/21/11 20:40, Rich Freeman wrote:
> On Wed, Sep 21, 2011 at 12:34 PM, Thomas Kahle <tomka@gentoo.org>
> wrote:
>> Let's have a page in our docs where everybody can explain his or
>> her tool.  Where in the hierarchy should the page be?  How
>> about: http://www.gentoo.org/proj/en/base/arch-testing
> 
> Please!  And the documentation should include examples of common 
> workflows, not just a dump of command line options and what they
> do.

First we need to gather everything to a single location.

> 
> Let's start with the use case of I have a stablereq for a package
> and I want to test it.  Just tell me how to do it, and don't make
> me figure out which combination of options works best.
It is a bit hard to document a generic testing process. Each package
has different requirements. We tried to document a generic workflow in
amd64 AT[1] and in the AT quiz as well.

 Oh, and make sure
> the instructions include any necessary cleanup if the process
> leaves cruft in package.keywords/etc.
Well cleanup process if a bit obvious for an experienced power user
like an AT.

[1]: http://www.gentoo.org/proj/en/base/amd64/at/index.xml
- -- 
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iQIcBAEBCgAGBQJOejAYAAoJEPqDWhW0r/LCZk4QAI0/C6VxF5ktw42GcLDPMHlk
74vfyJ2EGSXiDWkX1xINRy9ElGtfoXEdvVF3hN+TVGb+nyXqmR3FC1O5gY9CrxxW
dZCKdf2bXiW7eAvmgXkUUnyUUBhUkKM51OIFWlkiO/dGskAeWJTXz0svzfOeY2XO
ks3cKFveY/DjgHNmKeN+h0G0e8pwn8nEY90C/ecsI4Y8SvEknagnEosekm9XHdYv
fJL26Z9D17LnIqNbFaxsHDTmUcT1O10KvM+QqBWLKTSn900thCrnyBdTPMaFFjUj
hVadM4wdItNppuSbwU1wJxfmHE234U42oQ2lPkS5TRz5a0PyhfrTZIJr6QCjTk59
n2tLv7fwy0g5HDcqp9w2j8ToIcw45hMzWdb3MMSDSatqspSXjX+bD1Wuqv5EBf13
u1Nj6dMnM4c6fs4EcWANzfeO8HFhmzhLnudAZKRafB3GvCOMlimz3jSOOb+K8sEY
eY3wYWqbcQxXWJqT1vHcUgHPp0WZYLawXDLm5Ka9XOvqz8h+AFI432xBQNhDKHGV
jLLwe8gRE63sANKX8xkSY7gJj1odJjpOFddSU/r4rnQjOrcT14uKDBRE8PFiyuIr
NptrFN6/tSxj27b26G+JAO3EAcdxe1dL9BmRCdPMO5l2ThLGdnLbxJIsonthgj3n
o9ern/pOM6uncVG+KlTv
=dCo3
-----END PGP SIGNATURE-----

Re: [gentoo-dev] finding reverse dependencies for arch testing (and other purposes)

[Rich Freeman]

On Wed, Sep 21, 2011 at 2:42 PM, Markos Chandras <hwoarang@gentoo.org> wrote:
> It is a bit hard to document a generic testing process. Each package
> has different requirements. We tried to document a generic workflow in
> amd64 AT[1] and in the AT quiz as well.

Sure, and that's pretty much the method I use, and I imagine most arch
testers/devs use.  However, in most cases I tend to just find it
easier to do everything manually than to use the tools, even though I
might want to use a tool.  I guess the AT job just isn't that hard to
begin with, and the last thing I want is some tool posting in bugs or
committing something because I didn't catch something in the
documentation.

Rich