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

Testing removal summary 2015-08-09 (Sunday)



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

  REMOVED: beets 1.3.8+dfsg-2
    <http://release.debian.org/britney/hints/auto-removals>
    Bug #792060: FTBFS: tests fail: test_read_audio_properties (test_mediafile.AlacTest

  REMOVED: designate 2015.1.0-1
    <http://release.debian.org/britney/hints/auto-removals>
    Bug #792034: designate: Package is missing designate services

  REMOVED: gri 2.12.23-8
    <http://release.debian.org/britney/hints/auto-removals>
    Bug #790526: FTBFS: Fatal error occurred, no output PDF file produced

  REMOVED: tuskar-ui 0.1.0-2
    <http://release.debian.org/britney/hints/auto-removals>
    Bug #792071: FTBFS: most tests fail: from tuskarclient.v1 import overcloud_roles: ImportError: No module named v1

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

  HINTED FOR REMOVAL: gtkmathview 0.8.0-10+nmu2
    <http://release.debian.org/britney/hints/auto-removals>
    Bug #791052: gmetadom: library transition may be needed when GCC 5 is the default
    # in gmetadom
    Bug #785485: gtkmathview: FTBFS: error: template with C linkage

  HINTED FOR REMOVAL: libav 6:11.4-2
    <http://release.debian.org/britney/hints/pochu>
    #20150727
    # we're transitioning to ffmpeg

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: