[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#908947: youtube-dl: backport youtube-dl to recent version for stretch



Em 12 de outubro de 2018 17:09:18 BRT, Holger Levsen <holger@layer-acht.org> escreveu:
>Dear Rogério, dear release team, dear backports-admins,
>
>On Sun, Sep 16, 2018 at 02:57:30PM +0200, Thierry wrote:
>> Package: youtube-dl
>> Version: 2017.05.18.1-1
>> Severity: grave
>> Justification: renders package unusable
>> 
>> Dear Maintainer,
>> 
>> the version of youtube-dl that is shipped with stretch does not work
>> anymore for the youtube website, making the package unusable for some
>> videos. It should be updated to a more recent version. If this is not
>> possible by Debian policy, stretch-backport should provide a recent
>> version.
>
>(it's not only youtube that's broken but also others..)
>
>For the 2nd time in 2 months today I have installed a local backport of
>youtube-dl on my machine (and soon will do the same at friends...) so
>by
>now I'm also pretty close to upload youtube 2018.09.10-1~bpo9+1 to
>stretch-backports to solve this (better) for "me" (and others) but then
>I really do believe this should be fixed by uploading
>2018.09.10-1~deb9u1 to stable(-updates).
>
>what's your stance on this? 
>
>I'm happy to prepare uploads to either if that helps. (and a proper bug
>if the stable updates route is chosen.)

Dear Holger and release team,

First of all, sorry for the short answer, but I am using my phone.

Second, I would like to more formally update youtube-dl for stable releases in conjunction with Holger.

The justification is that the package is very volatile and breaks every few weeks according to changes of the sites that it supports (and there are some big names besides YouTube itself).

Besides that, at least one other "important" package (namely, mpv) depends on youtube-dl.

So, what is the way to proceed with updates to stable releases? I've never done that before.

Thanks,

Rogério Brito.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Reply to: