Skip to content

Update dockerfile to trixie#688

Closed
sjrct wants to merge 2 commits into
whipper-team:developfrom
sjrct:update-dockerfile-to-trixie
Closed

Update dockerfile to trixie#688
sjrct wants to merge 2 commits into
whipper-team:developfrom
sjrct:update-dockerfile-to-trixie

Conversation

@sjrct

@sjrct sjrct commented Jun 14, 2026

Copy link
Copy Markdown
Contributor

My motivation for this is was that the version of musicbrainzngs provided by the package in debian:buster was less that 0.7, causing this warning to appear:

WARNING:whipper.command.main:Parameter 'use_https' is missing in versions of musicbrainzngs < 0.7. This means whipper will only be able to communicate with the configured MusicBrainz server ('musicbrainz.org') over plain HTTP. If a custom server which speaks HTTPS only has been declared, a suitable version of the musicbrainzngs module will be needed to make it work in whipper.

The version in trixie (current stable) is 0.7.1 (most recent version) so this issue no longer occurs. buster also reached end of life in 2022, so prob best to update.

@sjrct
sjrct force-pushed the update-dockerfile-to-trixie branch 2 times, most recently from 2c7046a to bb7f5de Compare June 14, 2026 01:19
sjrct added 2 commits June 13, 2026 21:19
Signed-off-by: Chris Harding <sjrct@users.noreply.github.com>
Signed-off-by: Chris Harding <sjrct@users.noreply.github.com>
@sjrct
sjrct force-pushed the update-dockerfile-to-trixie branch from bb7f5de to e0ee988 Compare June 14, 2026 01:20
@MerlijnWajer

Copy link
Copy Markdown
Collaborator

Thanks. How does this compare to #668 - did you test this and confirm rips to be working?

@sjrct

sjrct commented Jun 14, 2026

Copy link
Copy Markdown
Contributor Author

Thanks. How does this compare to #668 - did you test this and confirm rips to be working?

@MerlijnWajer Oh, well, I suppose I should have checked if a PR for this already existed! 😅

That looks better than my PR, so I'll close this. I was able to rip with this PR, but I was also able to fix the two issues I encountered with that PR (see #689).

@sjrct sjrct closed this Jun 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants