3 files changed, 30 insertions, 5 deletions
diff --git a/network/youtube-dl/youtube-dl.1 b/network/youtube-dl/youtube-dl.1
index 2b5c7d90a8c02..ad5aa906d7791 100644
--- a/network/youtube-dl/youtube-dl.1
+++ b/network/youtube-dl/youtube-dl.1
@@ -428,7 +428,7 @@ Write video annotations to a .annotations.xml file
 .RS
 .RE
 .TP
-.B \-\-load\-info \f[I]FILE\f[]
+.B \-\-load\-info\-json \f[I]FILE\f[]
 JSON file containing the video information (created with the
 "\-\-write\-info\-json" option)
 .RS
@@ -1037,6 +1037,10 @@ download, starting at zero
 .IP \[bu] 2
 \f[C]playlist_index\f[]: Index of the video in the playlist padded with
 leading zeros according to the total length of the playlist
+.IP \[bu] 2
+\f[C]playlist_id\f[]: Playlist identifier
+.IP \[bu] 2
+\f[C]playlist_title\f[]: Playlist title
 .PP
 Available for the video that belongs to some logical chapter or section:
 \- \f[C]chapter\f[]: Name or title of the chapter the video belongs to
@@ -1670,6 +1674,27 @@ to a video or unsupported.
 You can find out which by examining the output (if you run youtube\-dl
 on the console) or catching an \f[C]UnsupportedError\f[] exception if
 you run it from a Python program.
+.SH Why do I need to go through that much red tape when filing bugs?
+.PP
+Before we had the issue template, despite our extensive bug reporting
+instructions (#bugs), about 80% of the issue reports we got were
+useless, for instance because people used ancient versions hundreds of
+releases old, because of simple syntactic errors (not in youtube\-dl but
+in general shell usage), because the problem was alrady reported
+multiple times before, because people did not actually read an error
+message, even if it said "please install ffmpeg", because people did not
+mention the URL they were trying to download and many more simple,
+easy\-to\-avoid problems, many of whom were totally unrelated to
+youtube\-dl.
+.PP
+youtube\-dl is an open\-source project manned by too few volunteers, so
+we\[aq]d rather spend time fixing bugs where we are certain none of
+those simple problems apply, and where we can be reasonably confident to
+be able to reproduce the issue without asking the reporter repeatedly.
+As such, the output of \f[C]youtube\-dl\ \-v\ YOUR_URL_HERE\f[] is
+really all that\[aq]s required to file an issue.
+The issue template also guides you through some basic steps you can do,
+such as checking that your version of youtube\-dl is current.
 .SH DEVELOPER INSTRUCTIONS
 .PP
 Most users do not need to build youtube\-dl and can download the
diff --git a/network/youtube-dl/youtube-dl.SlackBuild b/network/youtube-dl/youtube-dl.SlackBuild
index bf95af2932112..954350231ee2e 100644
--- a/network/youtube-dl/youtube-dl.SlackBuild
+++ b/network/youtube-dl/youtube-dl.SlackBuild
@@ -24,7 +24,7 @@
 #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 PRGNAM=youtube-dl
-VERSION=${VERSION:-2016.06.03}
+VERSION=${VERSION:-2016.06.11.3}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
diff --git a/network/youtube-dl/youtube-dl.info b/network/youtube-dl/youtube-dl.info
index 8a17dab6f8943..81737d9b8ca8e 100644
--- a/network/youtube-dl/youtube-dl.info
+++ b/network/youtube-dl/youtube-dl.info
@@ -1,8 +1,8 @@
 PRGNAM="youtube-dl"
-VERSION="2016.06.03"
+VERSION="2016.06.11.3"
 HOMEPAGE="https://rg3.github.io/youtube-dl"
-DOWNLOAD="https://github.com/rg3/youtube-dl/archive/2016.06.03.tar.gz"
-MD5SUM="b7401413b0e97a73e4871951e2857d82"
+DOWNLOAD="https://github.com/rg3/youtube-dl/archive/2016.06.11.3.tar.gz"
+MD5SUM="4e1e3b3253d95c30a31cab74765c3868"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""