-
-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add patch fixing up segment muxer #10
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit - the commit messages aren't clear why the patch is needed. Also lacks a link to the upstream contribution.
Patch segment muxer in ffmpeg
This is necessary to fix xyz until it is fixed upstream.
Upstream contribution can be tracked at.
@joshuaboniface commit message, not pull request description. Pull request messages aren't included in the actual git repository AFAIK. Use |
Or, not, I thought it did. That's stupid. |
52b32d1
to
6e95dfb
Compare
Manual patch required until the relevant patch is accepted upstream. Tracking at http://ffmpeg.org/pipermail/ffmpeg-devel/2019-October/250920.html
6e95dfb
to
959f377
Compare
RUN \ | ||
DIR=/tmp/ffmpeg && mkdir -p ${DIR} && cd ${DIR} && \ | ||
for patch in *.patch; do \ | ||
filename="$( grep '+++' ${patch} | awk '{ print $2 }' | sed 's|jellyfin-ffmpeg/||' )"; \ | ||
patch --verbose ${filename} ${patch}; \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Heh, why not just patch -p1 < "$patch"
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For whatever reason, the patch command wasn't liking the Debian patch format, mostly because the actual path to the file was different (we're one level lower at this stage). This makes it super explicit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But that is what -pN
does - it drops first N
dirs in a path before applying the patch...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also your method would fail for multi-file patches...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh really? OK, yea, that's nicer. I went through the man page quickly and didn't see the obvious solution. I guess that's an improvement to be made if we implement any more patches ;-) Hopefully we don't and this is redundant before then anyways.
For future reference, here's better upstream tracker URL: https://patchwork.ffmpeg.org/patch/15492/ |
Closes #9
Fixes jellyfin/jellyfin#1694
Re-implementation of #9 as a Debian source patch (rather than a manual patch). Also includes the porting of this patch to the Docker ffmpeg build.
Manual patch required until the relevant patch is accepted upstream. Tracking at http://ffmpeg.org/pipermail/ffmpeg-devel/2019-October/250920.html