[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Packages failing to be removed from testing

Analysis of packages trying to be removed from testing that just won't

> trying: -animals
> skipped: -animals (0 <- 177)
>     got: 189+0: a-41:a-43:h-41:i-64
>     * i386: junior-games-text

Package: junior-games-text
Testing: 1.3
Unstable: 1.3
Suggestion: remove-from-testing
Analysis: The maintainer of animals has uploaded a new version of the
 package, but it FTBFS on all other architectures.  The
 junior-games-text package should be trivially fixable to not depend on
 animals, or animals could be NMUed to trivially fix the FTBFS.

> trying: -cl-uncommonsql
> skipped: -cl-uncommonsql (1 <- 176)
>     got: 189+0: a-41:a-43:h-41:i-64
>     * i386: cl-local-time-db

Package: cl-uncommonsql
Unstable: 1.2.1-1
Suggestion: don't-remove-from-testing
Analysis: in addition to cl-local-time-db, cl-metadata also has a
 dependency on both of the preceding packages.  The original RC bug
 against cl-uncommonsql, 186521, has since been fixed; there's no longer
 any reason to try to kick this package (and its dependents) out of
 testing, as the updated version should trivially make its way in once
 this block is removed.

> trying: -curl-ssl
> skipped: -curl-ssl (2 <- 175)
>     got: 385+0: a-41:a-43:h-41:i-63:i-41:m-43:m-37:m-36:p-40
>     * i386: php4-curl
>     * powerpc: php4-curl

Package: curl-ssl
Testing: 7.9.5-2
Unstable: none
Suggestion: yank-it-out-by-the-roots
Analysis: PHP is already a mess in testing, and this package needs to go
 -- one more broken dependency won't hurt anything.  Or if it's easier,
 it can languish a bit longer until php4 4.3 makes it in.

> trying: -eel
> skipped: -eel (3 <- 174)
>     got: 44+0: a-44
>     * alpha: galeon-nautilus, libnautilus-dev, nautilus

Suggestion: wait-and-see
Analysis: package superseded by eel2, and has already been removed from
 unstable; just waiting on galeon and nautilus to be up-to-date in

> trying: -gimp1.2
> skipped: -gimp1.2 (4 <- 173)
>     got: 51+0: a-51
>     * alpha: exult-studio, gimp-dimage-color, gimp-python, gimp1.2-print, gimp1.2-quiteinsane, gtkam-gimp, mtink, sane, xpcd-gimp, xsane

Suggestion: wait-and-see
Analysis: Needs removing, but needs the new gimp package to be ready for
 testing first to satisfy all the dependencies on libgimp1.2.  Give it a
 few days for gcc-3.3 to clear up.

> trying: -gnome-core
> skipped: -gnome-core (5 <- 172)
>     got: 52+0: a-52
>     * alpha: galeon-nautilus, gnome-admin, gnome-media, gnome-pilot, gnome-pilot-conduits, gnome-pim-conduits, gnomeicu, ickle-gnome, libpanel-applet-ruby, nautilus, seti-applet

Suggestion: wait-and-see
Analysis: Replaced by meta-gnome2, which is also not yet ready for
 testing.  Revisit next week to see how the GNOME dependencies are
 coming along.

> trying: -gnome-guile
> skipped: -gnome-guile (6 <- 171)
>     got: 42+0: a-42
>     * alpha: gwave

Package: gwave
Testing: 20020122-1
Unstable: 20020122-1
Bugs: 187829
Suggestion: remove-from-testing
Analysis: Package depended on libguilegtk0, which has been removed from
 unstable and is therefore unmaintained in testing.  The gwave package
 has a 5-month-old grave bug open about this issue, with no sign of

> trying: -gnome-pilot
> skipped: -gnome-pilot (7 <- 170)
>     got: 43+0: a-43
>     * alpha: gnome-pilot-conduits, gnome-pim-conduits

The dangers of alphabetization.  The gnome-pilot-conduits and gnome-pim
packages were removed immediately after this failure, so this should
sort itself out tomorrow.

> trying: -id3lib
> skipped: -id3lib (0 <- 175)
>     got: 43+0: a-43
>     * alpha: grip, xmms-singit

Suggestion: wait-and-see
Analysis: grip and xmms-singit have already been rebuild against the
 library from the new source package, id3lib3.8.3.  More of the same
 waiting game.

> trying: -java-virtual-machine-dummy
> skipped: -java-virtual-machine-dummy (1 <- 174)
>     got: 191+0: a-41:a-43:h-41:i-66
>     * i386: jmeter, tomcat4, tomcat4-webapps

Package: java-virtual-machine-dummy
Testing: 0.3
Unstable: none
Suggestion: yank-it-out-by-the-roots
Analysis: These three packages are all in contrib, and the dependency
 should therefore be ignorable. (java-virtual-machine-dummy is also the
 last in a list of dependency-satisfying alternatives for the packages.)

> trying: -jsboard
> skipped: -jsboard (2 <- 173)
>     got: 195+0: a-41:a-43:h-41:i-70
>     * i386: jsboard-theme-aicom-ko, jsboard-theme-debian-ko, jsboard-theme-diary-en, jsboard-theme-diary-ko, jsboard-theme-trash-en, jsboard-theme-trash-ko, jsboard-theme-wizz-ko

Package: jsboard-theme-aicom-ko, jsboard-theme-debian-ko, jsboard-theme-diary-en, jsboard-theme-diary-ko, jsboard-theme-trash-en, jsboard-theme-trash-ko, jsboard-theme-wizz-ko
Testing: 0.5-1
Unstable: 0.5-1
Suggestion: remove-from-testing
Analysis: Depend on a package we want to remove; these packages are not
 useful without jsboard itself.

> trying: -kernel-image-2.2.20-i386
> skipped: -kernel-image-2.2.20-i386 (3 <- 172)
>     got: 191+0: a-41:a-43:h-41:i-66
>     * i386: pcmcia-modules-2.2.20, pcmcia-modules-2.2.20-compact, pcmcia-modules-2.2.20-idepci

Package: pcmcia-cs
Testing: 3.1.33-6
Unstable: 3.2.2-1.1
Bugs: 170188, 198285
Suggestion: ??
Analysis: The pcmcia modules package seems to be a bit of a mess; 180
 days out of date in testing, despite not having any of the usual
 excuses (glibc, gcc).  The package casts a very wide net of
 dependencies, so any one kernel package disappearing from the archive
 causes problems (as in the case above).  Requires further investigation
 and probably an NMU.
 An additional RC bug affects the package version currently in

> trying: -kernel-image-2.4.20-3-i386
> skipped: -kernel-image-2.4.20-3-i386 (4 <- 171)
>     got: 209+0: a-41:a-43:h-41:i-84
>     * i386: alsa-modules-2.4.20-3-386, alsa-modules-2.4.20-3-586tsc, alsa-modules-2.4.20-3-686, alsa-modules-2.4.20-3-686-smp, alsa-modules-2.4.20-3-k6, alsa-modules-2.4.20-3-k7, alsa-modules-2.4.20-3-k7-smp, i2c-2.4.20-3-386, i2c-2.4.20-3-586tsc, i2c-2.4.20-3-686, i2c-2.4.20-3-686-smp, i2c-2.4.20-3-k6, i2c-2.4.20-3-k7, i2c-2.4.20-3-k7-smp, linux-wlan-ng-modules-2.4.20-3-386, linux-wlan-ng-modules-2.4.20-3-586tsc, linux-wlan-ng-modules-2.4.20-3-686, linux-wlan-ng-modules-2.4.20-3-686-smp, linux-wlan-ng-modules-2.4.20-3-k6, linux-wlan-ng-modules-2.4.20-3-k7, linux-wlan-ng-modules-2.4.20-3-k7-smp

Same melody as the preceding, just in a different key.  There's a fair
amount of recompilation work needed here.

> trying: -kernel-source-2.2.20
> skipped: -kernel-source-2.2.20 (5 <- 170)
>     got: 189+0: a-41:a-43:h-41:i-64
>     * i386: kernel-patch-2.2.20-powerpc

Package: kernel-patch-2.2.20-powerpc
Testing: 2.2.20-3
Unstable: 2.2.20-3
Suggestion: remove-from-testing, remove-from-unstable
Analysis: The 2.4 kernels seem to be well supported for powerpc; the
 removal of the 2.2.20 sources from unstable doesn't seem to have caused
 a stir, so this package can probably also go without being missed.

> trying: -kgeo
> skipped: -kgeo (6 <- 169)
>     got: 189+0: a-41:a-43:h-41:i-64
>     * i386: junior-kde
> trying: -kstars
> skipped: -kstars (7 <- 168)
>     got: 189+0: a-41:a-43:h-41:i-64
>     * i386: junior-kde

Package: junior-kde
Testing: 1.1
Unstable: 1.1
Suggestion: remove-from-testing
Analysis: The new kdeedu package that provides both kgeo and kstars is
 out of sync in unstable, and has been since Jun 5.  In the meantime,
 the old versions of these packages are helping to hold up the removal
 of various old KDE libs as well.  The junior-kde package can be removed
 from testing to clean this up, or we can wait for kdeedu to be
 installable in testing.

> trying: -libapache-mod-perl
> skipped: -libapache-mod-perl (8 <- 167)
>     got: 46+0: a-46
>     * alpha: axkit, libapache-authensmb, libapache-db-perl, libapache-request-perl, logtrend-visuapache

Suggestion: wait-and-see
Analysis: In unstable, libapache-mod-perl comes from the apache source
 package, which currently has two RC bugs (209276, 207453) and is held
 up by gcc.

> trying: -libmime-base64-perl
> skipped: -libmime-base64-perl (9 <- 166)
>     got: 42+0: a-42
>     * alpha: sympa

Suggestion: wait-and-see
Analysis: sympa is out of date on hppa due to the glibc problems there.
 There is an RC bug on sympa which may or may not still be applicable --
 and may or may not even affect the version currently in testing.  Have
 followed up to the bug, but otherwise think this is a wait-and-see for
 the moment.

> trying: -librsvg
> skipped: -librsvg (10 <- 165)
>     got: 46+0: a-46
>     * alpha: galeon-nautilus, libeel-dev, libeel0, libnautilus-dev, nautilus

Suggestion: wait-and-see
Analysis: Just as eel is superseded by eel2, this package has been
 superseded by librsvg2, and is waiting for the same reason.

> trying: -libweakref-perl
> skipped: -libweakref-perl (11 <- 164)
>     got: 194+0: a-41:a-43:h-41:i-69
>     * i386: libxml-twig-perl, libxmltv-perl, libxtm-perl, xmltv, xmltv-gui, xmltv-util

Suggestion: wait-and-see
Analysis: Removed from unstable, can't be removed from testing until a
 few more packages are brought up to date.

> trying: -medusa
> skipped: -medusa (12 <- 163)
>     got: 45+0: a-45
>     * alpha: galeon-nautilus, libnautilus-dev, libnautilus0, nautilus

Suggestion: wait-and-see
Analysis: Removed from unstable, caught up in the whole nautilus chain.

> trying: -omniorb
> skipped: -omniorb (13 <- 162)
>     got: 50+0: a-50
>     * alpha: 3dwm-clock, 3dwm-csgclient, 3dwm-geoclient, 3dwm-pickclient, 3dwm-server, 3dwm-texclient, 3dwm-vncclient, libnobel, libnobel-dev

Suggestion: wait-and-see
Analysis: Removed from unstable and superseded by omniorb4, which is
 already in testing.  The 3dwm package is just being held up by gcc at
 this point, after which this should disappear on its own.

> trying: -orp
> skipped: -orp (14 <- 161)
>     got: 189+0: a-41:a-43:h-41:i-64
>     * i386: orp-classpath

Package: orp-classpath
Testing: 1:0.02.1-3
Unstable: 1:0.02.1-3
Suggestion: remove-from-testing
Analysis:  When requesting orp's removal, Colin wrote, "Note that
 orp-classpath depends on this, but is obviously useless itself with a
 broken orp."

> trying: -pd
> skipped: -pd (15 <- 160)
>     got: 42+0: a-42
>     * alpha: gem

Suggestion: wait-and-see
Analysis: Package renamed to 'puredata' in unstable, and should
 propagate into testing soon; gem, however, is being held out of testing
 by a FTBFS on alpha (and possibly another one on hppa, though the hppa
 buildd doesn't seem to have attempted the latest version of this
 package).  A bug has been filed for the alpha failure.

> trying: -php4
> skipped: -php4 (16 <- 159)
>     got: 47+0: a-47
>     * alpha: apl, php-cgiwrap, php-imlib, php4-apc, php4-dbase, php4-dbtcp, php4-gd2, php4-mcrypt, snui-server

Package: php4
Suggestion: don't-remove-from-testing
Analysis: Obviously, php4 is resisting removal.  Given that it's not
 coming out, the original motivation for trying to remove it no longer
 applies, and it's better to focus again on getting the newer version of
 the package into testing.

> trying: -pike
> skipped: -pike (17 <- 158)
>     got: 44+0: a-44
>     * alpha: libroxen-floatingcode, libroxen-form, roxen

Suggestion: wait-and-see
Analysis: Now provided by pike7.2 source package in unstable, which is
 held up by gcc.  Hopefully we'll see some movement soon.

> trying: -pike7
> skipped: -pike7 (18 <- 157)
>     got: 190+0: a-41:a-43:h-41:i-65
>     * i386: roxen2, roxen2-ssl

Suggestion: wait-and-see
Analysis: In bug 166311, the roxen2 maintainer admits that this package
 is "dead upstream".  I've followed up to point out it is now
 uninstallable in sid, asking whether these packages should be shipped
 with sarge.

> trying: -plib1.5
> skipped: -plib1.5 (19 <- 156)
>     got: 42+0: a-42
>     * alpha: tux-aqfh

Source package renamed to plib, which is currently held out of testing
because of a need for hinting related to the g++ transition.  I've added
a hint for plib, so plib, tuxkart, and flightgear should all go in
tomorrow.  That still leaves tux-aqfh in need of a recompile; bug filed.

> trying: -pspell
> skipped: -pspell (20 <- 155)
>     got: 42+0: a-42
>     * alpha: sylpheed-claws

Suggestion: wait-and-see
Analysis: The sylpheed-claws package has already been rebuilt against
 aspell in sid, and is waiting on dependencies right now.  Should
 resolve itself in due course.

> trying: -quicktime4linux
> skipped: -quicktime4linux (21 <- 154)
>     got: 196+0: a-41:a-43:h-41:i-71
>     * i386: fbtv, motv, scantv, streamer, ttv, webcam, xawtv, xawtv-plugins

Suggestion: wait-and-see
Analysis: The list of uninstallable packages seem to all point back to
 xawtv-plugins, which depended on libquicktime4linux0 in testing.  The
 version of xawtv in unstable is, in turn, waiting for the new version
 of libquicktime to be current on all archs before it propagates into
 testing.  The build failures on s390/arm appear to be caused by
 toolchain problems, not package bugs.

> trying: -ruby
> skipped: -ruby (22 <- 153)
>     got: 89+0: a-89
>     * alpha: eruby, libapache-mod-ruby, libdb-ruby, libdb2-ruby, libdb3-ruby, libdb4.1-ruby, libdbd-sqlite-ruby, libeb-ruby, liberuby, liberuby-dev, libexif-ruby, libfam-ruby, libgd-ruby, libgdk-imlib-ruby, libgdk-pixbuf-ruby, libglade-ruby, libgnome-ruby, libgtk-ruby, libiconv-ruby, libintl-gettext-ruby, libkakasi-ruby, libldap-ruby, libmysql-ruby, libncurses-ruby, libopenssl-ruby, libpanel-applet-ruby, libpcap-ruby, libpgsql-ruby, libsdl-ruby, libshadow-ruby, libstrscan-ruby, libsufary-ruby, libtmail-ruby, libuconv-ruby, libvorbisfile-ruby, libwidestudio-dev, libwidestudio-ruby, libwrap-ruby, libxml-parser-ruby, libxmms-ruby, libzlib-ruby, mhc-utils, quantlib-ruby, racc-runtime, rubymagick, vim-ruby, widestudio, xmlrpc4r

Suggestion: wait-and-see
Analysis: at least some of the affected packages have been rebuilt
 against libruby1.8, and are waiting for the current version of that
 package to propagate into testing.  This should happen once gcc is
 cleared up, and we can take a fresh look at anything left afterwards.

> trying: -suidmanager
> skipped: -suidmanager (23 <- 152)
>     got: 42+0: a-42
>     * alpha: amavis-ng-milter-helper

Suggestion: um,-wtf
Analysis: If amavis-ng-milter-helper depends on suidmanager in testing,
 I'm not seeing it.  Is this a bug?

> trying: -uw-imap-ssl
> skipped: -uw-imap-ssl (24 <- 151)
>     got: 45+0: a-45
>     * alpha: php3-cgi-imap, php3-imap, php4-imap, postman

Suggestion: wait-and-see
Analysis: These packages have been rebuilt against uw-imap, but are
 waiting for that package to propagate into testing.  This appears to be
 another dependency waiting game.

> trying: -xanim
> skipped: -xanim (25 <- 150)
>     got: 189+0: a-41:a-43:h-41:i-64
>     * i386: tkxanim

From <20030909053946.EFDF11C93D@laptop.nahmias.net>:

Package: tkxanim
Testing: 0.43-6
Bugs: 208373
Suggestion: remove-from-testing, remove-from-unstable
  This package contains a Tcl/Tk interface to xanim.  xanim was removed
  from unstable because it was a long time orphaned non-free app that has
  since been replaces/superceded by xine.  As this package is useless
  without xanim, there doesn't seem much of a point keeping it around.
  N.B. tkxanim is the only reverse-dep on xanim; so after it is removed,
  both can/should be removed from testing.

> trying: -xerces
> skipped: -xerces (26 <- 149)
>     got: 45+0: a-45
>     * alpha: libapache-mod-xslt, libxalan1.2, libxalan1.2-dev, xalan

Suggestion: wait-and-see
Analysis: Package superseded by xerces21 in unstable.  libxalan1.2 is
 itself superseded by libxalan14 in unstable, which is waiting on
 xerces21, which is waiting on gcc.  Whole lotta waiting.  Once gcc is
 in, it looks like some hinting will be required here for

> trying: -xerces20
> skipped: -xerces20 (27 <- 148)
>     got: 42+0: a-42
>     * alpha: libxml-xerces-perl

Suggestion: wait-and-see
Analysis: The libxml-xerces-perl package is also waiting on xerces21
 above.  Nothing to be done.

Steve Langasek
postmodern programmer

Attachment: pgp16SUTc9U76.pgp
Description: PGP signature

Reply to: