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

Testing removal summary 2020-12-12 (Saturday)



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

  REMOVED: google-i18n-address 2.3.2-3
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #973175: google-i18n-address: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13

  REMOVED: odb-api 0.18.1-14
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #973119: odb-api: FTBFS: GribMetaData.h:23:10: fatal error: eckit/types/Metadata.h: No such file or directory

  REMOVED: python-boltons 19.1.0-2
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #973099: python-boltons: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13

  REMOVED: python-eliot 1.11.0-1
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #973099: python-boltons: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
    # in python-boltons

  REMOVED: ruby-redis-actionpack 5.2.0-2
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #973237: ruby-redis-rack: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: unknown keywords: :path, :domain, :expire_after, :secure, :httponly, :defer, :renew, :sidbits, :secure_random, :redis_server
    # in ruby-redis-rack

  REMOVED: ruby-redis-activesupport 5.2.0-1
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #973067: ruby-redis-activesupport: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: unknown keywords: :pool_size, :pool_timeout

  REMOVED: ruby-redis-rack 2.1.2-4
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #973237: ruby-redis-rack: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError: unknown keywords: :path, :domain, :expire_after, :secure, :httponly, :defer, :renew, :sidbits, :secure_random, :redis_server

  REMOVED: ruby-redis-rails 5.0.2-3
    <https://release.debian.org/britney/hints/auto-removals>
    # 973067,973237 in ruby-redis-activesupport,ruby-redis-rack

  REMOVED: slurm-llnl 19.05.5-2.1
    <https://release.debian.org/britney/hints/sramacher>
    # 20201211; done 20201211
    # slurm-wlm source package rename (#977117)

  REMOVED: txacme 0.9.2-2
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #973099: python-boltons: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
    # in python-boltons

  REMOVED: unison-2.48 2.48.4-8
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #973124: unison-2.48: FTBFS: ocamlc: OCaml has been configured with -force-safe-string: -unsafe-string is not available.

  REMOVED: xml2rfc 2.47.0-1
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #973175: google-i18n-address: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
    # in google-i18n-address

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

  HINTED FOR REMOVAL: python-biplist 1.0.3-2
    <https://release.debian.org/britney/hints/auto-removals>
    Bug #973082: python-biplist: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13

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: