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

Bug#943900: twolame breaks ffmpeg autopkgtest: twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.



Control: reassign -1 src:ffmpeg 7:4.1.4-1
Control: tags -1 upstream
Control: forwarded -1 https://ffmpeg.org/pipermail/ffmpeg-devel/2019-November/252392.html

Hi,

On 31/10/2019 21:18, Sebastian Ramacher wrote:
> On 2019-10-31 16:37:11, Paul Gevers wrote:
>> Source: twolame, ffmpeg
>> Control: found -1 twolame/0.4.0-2
>> Control: found -1 ffmpeg/7:4.2.1-1
>> Severity: serious
>> Tags: sid bullseye
>> X-Debbugs-CC: debian-ci@lists.debian.org
>> User: debian-ci@lists.debian.org
>> Usertags: breaks needs-update
>>
>> Dear maintainers,
>>
>> With a recent upload of twolame the autopkgtest of ffmpeg fails in
>> testing when that autopkgtest is run with the binary packages of twolame
>> from unstable. It passes when run with only packages from testing. In
>> tabular form:
>>                        pass            fail
>> twolame                from testing    0.4.0-2
>> ffmpeg                 from testing    7:4.2.1-1
>> all others             from testing    from testing
>>
>> I copied some of the output at the bottom of this report.
>>
>> Currently this regression is blocking the migration of twolame to
>> testing [1]. Due to the nature of this issue, I filed this bug report
>> against both packages. Can you please investigate the situation and
>> reassign the bug to the right package?
> 
> This is an issue in ffmpeg. The change in twolame is deliberate:
> https://github.com/njh/twolame/pull/32. The defaults in ffmpeg produce
> invalid files.

I submitted the above patch. I'll give it a few days to see what
upstream says about it before I upload it.

James

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: