FLV demuxer does not set duration for video packets

[rmk]

ffmpeg -f lavfi -i testsrc -t 1 test-1s.flv
ffprobe -show_entries packet=duration test-1s.flv

Output:
ffprobe version git-2015-11-25-e6fbe23 Copyright (c) 2007-2015 the FFmpeg developers
  built with Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn)
  configuration: --enable-shared --disable-static --disable-doc --disable-devices --enable-indev=lavfi --prefix=/Users/teamcity/buildAgent/work/3b1b1b1b725f407e/build/ffmpeg --extra-cflags=-I/Users/teamcity/buildAgent/work/3b1b1b1b725f407e/build/libmp3lame/include/ --extra-ldflags=-L/Users/teamcity/buildAgent/work/3b1b1b1b725f407e/build/libmp3lame/lib/ --extra-cflags=-I/Users/teamcity/buildAgent/work/3b1b1b1b725f407e/build/libogg/include/ --extra-ldflags=-L/Users/teamcity/buildAgent/work/3b1b1b1b725f407e/build/libogg/lib/ --extra-cflags=-I/Users/teamcity/buildAgent/work/3b1b1b1b725f407e/build/libvorbis/include/ --extra-ldflags=-L/Users/teamcity/buildAgent/work/3b1b1b1b725f407e/build/libvorbis/lib/ --extra-ldflags='-Wl,-rpath,@loader_path/../lib' --enable-libvorbis --enable-libvpx --enable-libmp3lame --enable-libopenh264 --enable-libfreetype
  libavutil      55.  9.100 / 55.  9.100
  libavcodec     57. 16.100 / 57. 16.100
  libavformat    57. 19.100 / 57. 19.100
  libavdevice    57.  0.100 / 57.  0.100
  libavfilter     6. 15.100 /  6. 15.100
  libswscale      4.  0.100 /  4.  0.100
  libswresample   2.  0.101 /  2.  0.101
Input #0, flv, from 'test-1s.flv':
  Metadata:
    encoder         : Lavf57.19.100
  Duration: 00:00:01.00, start: 0.000000, bitrate: 437 kb/s
    Stream #0:0: Video: flv1, yuv420p, 320x240, 200 kb/s, 25 fps, 25 tbr, 1k tbn, 1k tbc
[PACKET]
duration=N/A
[/PACKET]
[PACKET]
duration=N/A
[/PACKET]
...

[Hendrik]

Packet duration in the demuxer is available only in very few formats, and without really knowing if FLV as a format has it, its not a value you should generally rely on being present.

[rmk]

Sorry, forget it. Just read up on it and the FLV format does not contain this information in the first place, so the bug report is invalid.