Bug#905050: mpv: why does mpv tell it's built on unknown [PATCH]
Control: tags -1 + patch
[resending as debbugs seems to have ignored my first attempt]
One way of fixing this bug is to set the BUILDDATE variable
based on the timestamp of the most recent debian changelog entry.
That way BUILDDATE contains a sane date instead of "UNKNOWN",
but the build is reproducible (all builds from the same source
package version will have the same date).
Patch attached below. In order for it to take effect, it is
necessary to remove --disable-build-date option in debian/rules,
i.e. revert the patch from https://bugs.debian.org/784267
--- a/version.sh
+++ b/version.sh
@@ -53,7 +53,7 @@
NEW_REVISION="#define VERSION \"${VERSION}\""
OLD_REVISION=$(head -n 1 "$version_h" 2> /dev/null)
-BUILDDATE="#define BUILDDATE \"$(date)\""
+BUILDDATE="#define BUILDDATE \"$(date -u --date=@$(dpkg-parsechangelog -S
Timestamp))\""
MPVCOPYRIGHT="#define MPVCOPYRIGHT \"Copyright © 2000-2018
mpv/MPlayer/mplayer2 projects\""
# Update version.h only on revision changes to avoid spurious rebuilds
Bug#905050: mpv: why does mpv tell it's built on unknown
Hi, On 01/08/18 03:16, shirish शिरीष wrote: > On 31/07/2018, James Cowgill wrote: >> On 31/07/18 07:07, shirish शिरीष wrote: >>> At times when I'm running a video, I get this ffmpeg warning - >>> >>> [ffmpeg] NULL: Failed to parse extradata >>> >>> and have no idea why that error triggrs. >> >> Probably a broken input file. Does this only happen for some files? > > With quite a few more media files than I care to admit. It could be > something that a newer encoder could fix when encoding a media file, > dunno what. I'll try to see if somebody knows a better de-bugging way > so I know what's missing or broken and try to see if there is > something that needs fixing. Can you try playing the file with ffplay? If you get the same warning then at least it's nothing to do with mpv. = Incidentally I notice this upstream PR which would remove the "built on UNKNOWN" line and therefore fix the first part of the bug report: https://github.com/mpv-player/mpv/pull/6046 Maybe they saw this bug :P James signature.asc Description: OpenPGP digital signature
Bug#905050: mpv: why does mpv tell it's built on unknown
at bottom :- On 31/07/2018, James Cowgill wrote: > Hi, > > On 31/07/18 07:07, shirish शिरीष wrote: > >> At times when I'm running a video, I get this ffmpeg warning - >> >> [ffmpeg] NULL: Failed to parse extradata >> >> and have no idea why that error triggrs. > > Probably a broken input file. Does this only happen for some files? > > James > With quite a few more media files than I care to admit. It could be something that a newer encoder could fix when encoding a media file, dunno what. I'll try to see if somebody knows a better de-bugging way so I know what's missing or broken and try to see if there is something that needs fixing. Please share if anybody from the debian-multimedia can help in identifying what could be done or info. found out . -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Bug#905050: mpv: why does mpv tell it's built on unknown
Hi, On 31/07/18 07:07, shirish शिरीष wrote: > Package: mpv > Version: 0.29.0-1 > Severity: normal > > Dear Maintainer, > > I was running - [...] > > what kinda stuck me mpv saying - > > [cplayer] built on UNKNOWN and that info. seems to indicate something > is wrong. This is because we build mpv with --disable-build-date for reproducible builds so the build date is "UNKNOWN". Probably it would be nicer if that line was completely omitted. > At times when I'm running a video, I get this ffmpeg warning - > > [ffmpeg] NULL: Failed to parse extradata > > and have no idea why that error triggrs. Probably a broken input file. Does this only happen for some files? James signature.asc Description: OpenPGP digital signature
Bug#905050: mpv: why does mpv tell it's built on unknown
Package: mpv Version: 0.29.0-1 Severity: normal Dear Maintainer, I was running - $ mpv -v [cplayer] Command line options: '-v' [cplayer] mpv 0.29.0 Copyright © 2000-2018 mpv/MPlayer/mplayer2 projects [cplayer] built on UNKNOWN [cplayer] ffmpeg library versions: [cplayer]libavutil 56.14.100 [cplayer]libavcodec 58.18.100 [cplayer]libavformat 58.12.100 [cplayer]libswscale 5.1.100 [cplayer]libavfilter 7.16.100 [cplayer]libswresample 3.1.100 [cplayer] ffmpeg version: 4.0.2-1 [cplayer] [cplayer] Configuration: ./waf configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --confdir=/etc/mpv --zshdir=/usr/share/zsh/vendor-completions --enable-cdda --enable-dvdnav --enable-dvdread --enable-libmpv-shared --enable-libsmbclient --enable-sdl2 --enable-sndio --enable-zsh-comp --disable-build-date --enable-dvbin [cplayer] List of enabled features: 52arch alsa asm atomics caca cdda cplayer cplugins debug-build drm drmprime dvbin dvdnav dvdread dvdread-common egl-drm egl-helpers egl-x11 fchmod ffmpeg gbm gbm.h gl gl-wayland gl-x11 glibc-thread-name glob glob-posix gnuc gpl iconv jack jpeg lcms2 libaf libarchive libass libass-osd libav-any libavcodec libavdevice libbluray libdl libm libmpv-shared librt libsmbclient linux-fstatfs lua optimize oss-audio plain-gl posix posix-or-mingw posix-spawn posix-spawn-native pthreads pulse rubberband sdl2 sndio stdatomic uchardet vaapi vaapi-drm vaapi-egl vaapi-glx vaapi-wayland vaapi-x-egl vaapi-x11 vdpau vdpau-gl-x11 vt.h vulkan wayland wayland-protocols x11 xv zlib zsh-comp [cplayer] Reading config file /etc/mpv/encoding-profiles.conf [cplayer] Reading config file /home/shirish/.config/mpv/mpv.conf [cplayer] mpv 0.29.0 Copyright © 2000-2018 mpv/MPlayer/mplayer2 projects [cplayer] built on UNKNOWN [cplayer] ffmpeg library versions: [cplayer]libavutil 56.14.100 [cplayer]libavcodec 58.18.100 [cplayer]libavformat 58.12.100 [cplayer]libswscale 5.1.100 [cplayer]libavfilter 7.16.100 [cplayer]libswresample 3.1.100 [cplayer] ffmpeg version: 4.0.2-1 [cplayer] what kinda stuck me mpv saying - [cplayer] built on UNKNOWN and that info. seems to indicate something is wrong. At times when I'm running a video, I get this ffmpeg warning - [ffmpeg] NULL: Failed to parse extradata and have no idea why that error triggrs. While the video works and everything, I am put off by that message and dunno who is to blame, either mpv, ffmeg or something else ? FWIW, the video and the sub. play right. -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (100, 'unstable-debug'), (100, 'experimental-debug'), (100, 'experimental'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mpv depends on: ii libarchive13 3.2.2-4.1 ii libasound21.1.6-1 ii libass9 1:0.14.0-2 ii libavcodec58 7:4.0.2-1 ii libavdevice58 7:4.0.2-1 ii libavfilter7 7:4.0.2-1 ii libavformat58 7:4.0.2-1 ii libavutil56 7:4.0.2-1 ii libbluray21:1.0.2-3 ii libc6 2.27-5 ii libcaca0 0.99.beta19-2+b3 ii libcdio-cdda2 10.2+0.94+2-2+b2 ii libcdio-paranoia2 10.2+0.94+2-2+b2 ii libcdio18 2.0.0-2 ii libdrm2 2.4.92-1 ii libdvdnav46.0.0-1 ii libdvdread4 6.0.0-1 ii libegl1 1.0.0+git20180308-3 ii libgbm1 18.1.4-1 ii libgl11.0.0+git20180308-3 ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-22.9-2 ii liblua5.2-0 5.2.4-1.1+b2 ii libpulse0 11.1-5 ii librubberband21.8.1-7 ii libsdl2-2.0-0 2.0.8+dfsg1-1 ii libsmbclient 2:4.8.2+dfsg-2 ii libsndio6.1 1.1.0-3 ii libswresample37:4.0.2-1 ii libswscale5 7:4.0.2-1 ii libuchardet0 0.0.6-3 ii libva-drm22.2.0-1 ii libva-wayland22.2.0-1 ii libva-x11-2 2.2.0-1 ii libva22.2.0-1 ii libvdpau1 1.1.1-8 ii libvulkan11.1.73+dfsg-1 ii libwayland-client01.15.0-2 ii libwayland-
