Debian Patches

Status for beets/1.6.0-9

Patch Description Author Forwarded Bugs Origin Last update
skip-broken-test Skip test_command_line_option_relative_to_working_dir Stefano Rivera <stefanor@debian.org> no 2018-03-12
skip-unreliable-tests Skip unreliable tests
Some tests sometimes fail (e.g. under autopkgtests)
Stefano Rivera <stefanor@debian.org> no 2018-08-12
skip-buildd-failures Skip tests that fail on buildds
Not entirely sure why they fail, as network requests are stubbed. Can't
reproduce locally.
Stefano Rivera <stefanor@debian.org> no 2019-12-25
unidecode-1.3.6 Adapt tests to latest Unidecode version
Unidecode 1.3.5 (a yanked PyPI version) changed the behavior of
Unidecode for some specific characters:

> Remove trailing space in replacements for vulgar fractions.

As luck would have it, our tests used the 1/2 character specifically to
test the behavior when these characters decoded to contain slashes. We
now pin a sufficiently recent version of Unidecode and adapt the tests
to match the new behavior.
Adrian Sampson <adrian@radbox.org> no upstream, https://github.com/beetbox/beets/commit/5ae1e0f3c8d3a450cb39f7933aa49bb78c2bc0d9 2022-10-01
mediafile-0.11 tests: fix assertions for empty MediaFile.images
used to work due to inconsistent mediafile implementation, but with
https://github.com/beetbox/mediafile/pull/64 (in mediafile >= 0.11.0)
list fields are None if non-existent, not the empty list
wisp3rwind <17089248+wisp3rwind@users.noreply.github.com> no upstream, https://github.com/beetbox/beets/pull/4593 2022-12-18
sphinx-extlinks Add missing placeholders to extlinks captions
Sphinx 6.0.0 changed extlinks to always require placeholders in link
captions. See https://github.com/sphinx-doc/sphinx/commit/93cf1a57d916a1ff96c8e8a0356d0256e40489ac
Jack Wilsdon <jack.wilsdon@gmail.com> no debian upstream, https://github.com/beetbox/beets/commit/2106f471affd1dab35b4b26187b9c74d034528c5 2022-12-31
test_ui-completions test_ui: Fix spurious warnings in completion test
probably an issue going back to the Python 2 -> 3 switch: `map` gives an
iterator nowadays so after the test case started iterating
BASH_COMPLETION_PATHS, print_completion() couldn't find the
(previously found) bash_completion anymore, and would log a spurious
warning about that.

Also, some cleaup of path type handling
wisp3rwind <17089248+wisp3rwind@users.noreply.github.com> no upstream, https://github.com/beetbox/beets/pull/4829/commits/26faf8daa9527216e106f8d9d5f59dc085cd7d9c 2023-06-24
python3.12-imp Remove use of `imp`
The replacements in `importlib.util` have been available since Python
3.5.
Adrian Sampson <adrian@radbox.org> no upstream, https://github.com/beetbox/beets/commit/63b7595bd4c1a6b3af9b86d741765c903c1a4232 2022-08-21
python3.12-has_calls has_calls -> assert_has_calls
AFAICT, `mock.has_calls` *never* existed. It only started emitting a
warning recently. And for some reason I only see this crop up on
Windows? Truly mysterious.
Adrian Sampson <adrian@radbox.org> no upstream, https://github.com/beetbox/beets/commit/cd3fca3d50ae8008f518dc8036fcb40fd0aa88e2 2023-10-20
python3.12-has_calls-2 Remove apparently-wrong assert
This assertion was silently a no-op for years, and it apparently fails.
So since we were not even testing it before, it is at least no worse to
just remove it.
Adrian Sampson <adrian@radbox.org> no upstream, https://github.com/beetbox/beets/commit/9e86162be0cf51ba175d5525381036f1f51a1454 2023-10-20
python3.12-inspect-mocking Fix `inspect` mocking
File this under "I have no idea how this *ever* worked"...
Adrian Sampson <adrian@radbox.org> no upstream, https://github.com/beetbox/beets/commit/a9e1b607c57962166bc89aea7a9638977f1e08d0 2023-10-20
python3.12-inspect-mocking-2 Better mocking for getfullargspec
Seems much more straightforward this way?
Adrian Sampson <adrian@radbox.org> no upstream, https://github.com/beetbox/beets/commit/cc0979692bd3c00e42b8f6e71c31d1c37ccf7246 2023-10-20
test-Ignore-test_get_single_item_by_path-partially.patch test: Ignore test_get_single_item_by_path() partially
The behaviour of this check is different with Werkezug >= 2.3 and will
fail starting with that version.
For now ignore the assert checking within this check in case the
Werkzeug version is greater than 2.3.x.
Should be not needed once a new version of beets will get released as a
version > 1.6.0.
Carsten Schoenert <c.schoenert@t-online.de> no 2024-01-03

All known versions for source package 'beets'

Links