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

Testing removal summary 2016-09-20 (Tuesday)



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

  REMOVED: aster 11.5.0+dfsg2-4
    <https://release.debian.org/britney/hints/pochu>
    # openmpi transition

  REMOVED: bbpager 0.4.7-3
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #835034: bbpager: FTBFS [amd64]: relocation R_X86_64_32S can not be used when making a shared object

  REMOVED: burp 1.4.40-2
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #835036: burp: FTBFS [i386]: Narrowing conversion

  REMOVED: ceres-solver 1.11.0~dfsg0-5
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #835037: ceres-solver: FTBFS with eigen3 >> 3.3~beta1

  REMOVED: elib.intl 0.0.3~git20110809-4
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #830551: elib.intl: accesses the internet during build

  REMOVED: espresso 5.1+dfsg-4
    <https://release.debian.org/britney/hints/pochu>
    # openmpi transition

  REMOVED: esys-particle 2.3.4+dfsg1-2
    <https://release.debian.org/britney/hints/pochu>
    # openmpi transition

  REMOVED: gourmet 0.17.4-3
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #830551: elib.intl: accesses the internet during build
    # in elib.intl

  REMOVED: libbitcoin 2.0-2.4
    <https://release.debian.org/britney/hints/pochu>
    # boost1.58 removal

  REMOVED: libblocksruntime 0.4.1-1
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #832015: libblocksruntime: FTBFS with -fdebug-prefix-map

  REMOVED: libtexttools 2.1.0-7
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #834248: libtexttools: FTBFS in testing

  REMOVED: lightspark 0.7.2+git20150512-2.1
    <https://release.debian.org/britney/hints/pochu>
    # boost1.58 removal

  REMOVED: mpqc3 0.0~git20160216-3
    <https://release.debian.org/britney/hints/pochu>
    # openmpi transition

  REMOVED: opensurgsim 0.6.0-5
    <https://release.debian.org/britney/hints/pochu>
    # boost1.58 removal

  REMOVED: tome 2.4~0.git.2015.12.29-1
    <https://release.debian.org/britney/hints/pochu>
    # boost1.58 removal

  REMOVED: vmmlib 1.0-2
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #834472: vmmlib: FTBFS: stdlib.h:774:12: error: expected unqualified-id before 'int'

  REMOVED: vowpal-wabbit 7.3-1.1
    <https://release.debian.org/britney/hints/pochu>
    # boost1.58 removal

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

  HINTED FOR REMOVAL: boost1.58 1.58.0+dfsg-5.1
    <https://release.debian.org/britney/hints/pochu>
    # boost1.58 removal

  HINTED FOR REMOVAL: icinga2 2.4.10-1
    <https://release.debian.org/britney/hints/pochu>
    # boost1.58 removal

  HINTED FOR REMOVAL: libvsqlitepp 0.3.13-3.1
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #809119: libvsqlitepp: FTBFS when built with dpkg-buildpackage -A (invalid package/library name)

  HINTED FOR REMOVAL: python-aiohttp 0.22.4-1
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #830567: python-aiohttp: accesses the internet during build

  HINTED FOR REMOVAL: zope2.13 2.13.22-1
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #806127: zope2.13: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

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: