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

Testing removal summary 2016-01-31 (Sunday)

The following source package(s) have been removed from testing:

  REMOVED: bind-dyndb-ldap 8.0-1
    Bug #809565: bind-dyndb-ldap: FTBFS: -Werror=date-time

  REMOVED: kgamma 4:4.14.2-1
    Package not in unstable

  REMOVED: libpdl-stats-perl
    Bug #805824: pdl: Fails to build with GSL 2
    # in pdl
    Bug #806981: libpdl-stats-perl: Update build dependencies for GSL 2.x

  REMOVED: lynx-cur 2.8.9dev8-1
    Package not in unstable

  REMOVED: openmcdf 1.5.4-2
    Bug #809589: openmcdf: FTBFS: Error initializing task Message: Not registered task Message.

  REMOVED: pegasus-wms 4.4.0+dfsg-4
    Bug #809591: pegasus-wms: FTBFS: error: switch quantity not an integer

  REMOVED: xchat 2.8.8-7.3
    Package not in unstable

The following package(s) appear to have valid removal hints,
but are still in testing for some reason:

  HINTED FOR REMOVAL: golang-gocheck 0.0~bzr20131118+85-2
    Bug #789991: FTBFS: Test failures including FixtureS.TestPanicOnSetUpSuite, FixtureS.TestPanicOnSetUpTest

  HINTED FOR REMOVAL: libopenobex 1.7.1-3
    # 20160118
    Bug #810604: RM: libopenobex/1.7.1-3
    Bug #810556: libopenobex1: soname change to libopenobex.so.2 without package rename

  HINTED FOR REMOVAL: nis 3.17-34
    Bug #800305: nis: Please migrate a supported debhelper compat level

The script that generates this mail tries to extract removal
reasons from comments in the britney hint files. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

Reply to: