Packages preventing other packages from going into testing
I have written a little Python program that analyses
http://ftp-master.debian.org/testing/update_excuses.html
to find out where the bottlenecks are for packages going into testing.
Essentially, it is a count of packages that directly and indirectly depend on
a package with at least one RC bug before they can go into testing.
This is the figure in the first column. The number in parentheses is the
number of packages that _only_ depend on this package before it can go into
testing.
My idea is to show where the low hanging fruits are, so that people able to
lend a hand know where to go.
If somebody thinks this is a useful utility, it is free for the asking. the
program can spit out exactly which packages are the depending ones as well.
That is just a matter of adding some more print statements.
Todays output looks like this:
129 ( 25) openldap2
81 ( 0) kdelibs
47 ( 47) phpgroupware-phpgroupware
45 ( 34) db3
35 ( 25) gnome-vfs2
27 ( 21) perl
23 ( 17) mozilla
20 ( 18) tetex-bin
15 ( 7) kaffe
15 ( 0) php4
13 ( 13) opie-comnet-fb
13 ( 8) guile-1.6
12 ( 1) libxfce4util
11 ( 0) libxfcegui4
11 ( 0) kdebase
8 ( 6) apt
8 ( 1) classpath
5 ( 4) pcmcia-cs
5 ( 1) aiksaurus
4 ( 0) krb4
3 ( 3) vdk2
3 ( 3) avifile
3 ( 3) gnue-common
2 ( 2) fsviewer
2 ( 2) oo2c
2 ( 2) mpich
2 ( 2) wvstreams
2 ( 1) hdf5
1 ( 1) gnet1.1
1 ( 1) paul
1 ( 1) erlang
1 ( 1) librudiments0
1 ( 1) gcc-3.2
1 ( 1) alsa-driver
1 ( 1) bigloo
1 ( 1) nvidia-kernel-src
1 ( 1) log4cpp
1 ( 1) nhc98
1 ( 1) openmosix
1 ( 1) crystalspace
1 ( 0) mozilla-snapshot
1 ( 0) vpopmail
1 ( 0) kdeadmin
1 ( 0) qcad
1 ( 0) xfce-mcs-plugins
1 ( 0) wordtrans
1 ( 0) galeon
1 ( 0) kdegraphics
1 ( 0) gnucash
1 ( 0) nautilus-media
1 ( 0) java-gnome
1 ( 0) lilypond
Reply to: