[FFmpeg-trac] #5057(avcodec:closed): master broke AVCodecContext compatibility with LibAV project

FFmpeg trac at avcodec.org
Fri Dec 4 18:26:05 CET 2015


#5057: master broke AVCodecContext compatibility with LibAV project
------------------------------------+-----------------------------------
             Reporter:  jyavenard   |                    Owner:
                 Type:  defect      |                   Status:  closed
             Priority:  normal      |                Component:  avcodec
              Version:  git-master  |               Resolution:  wontfix
             Keywords:              |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+-----------------------------------
Changes (by cehoyos):

 * status:  new => closed
 * resolution:   => wontfix
 * component:  undetermined => avcodec


Comment:

 Replying to [comment:16 jyavenard]:
 > Replying to [comment:12 cehoyos]:
 > > Replying to [ticket:5057 jyavenard]:
 > > > Please revert that commit
 > >
 > > We cannot revert this commit, it would brake binary compatibility.
 >
 > how so, as someone pointed out, 57 isn't set yet. I'm only looking into
 the future

 You misunderstand the FFmpeg versioning.
 We are at 57 already and it must not be changed (since more than a month).

 Yesterday, I had missed that the original commit changing the type of
 bitrate fixed one (or actually two iirc) real-world bug reports, so I will
 close this ticket as wontfix since the commit in question definitely
 cannot be reverted.

 > There's already sufficient changes in 57 that pretty much dropped every
 API we were using (get_buffer, memory allocation etc..)

 Do I understand correctly that this is unrelated?

 > > > Do you realise how many distributions our single binary package
 support
 > >
 > > Which distribution has the issue you are describing?
 >
 > currently none have an issue, we work with them all (but none of them
 ship with anything > 2.8).
 > I'm only looking ahead, for when master becomes 2.10 (or 2.9?) or
 whatever and it starts to be packaged and distributed.

 That is what I mean: Which distribution will be an issue for you in the
 future (once newer releases are available)?

--
Ticket URL: <https://trac.ffmpeg.org/ticket/5057#comment:24>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list