Package Details: youtube-dl-git 2021.02.22.r6.g1631fca1e-1

Git Clone URL: https://aur.archlinux.org/youtube-dl-git.git (read-only, click to copy)
Package Base: youtube-dl-git
Description: A small command-line program to download videos from YouTube.com and a few more sites (git version)
Upstream URL: http://ytdl-org.github.io/youtube-dl/
Keywords: download player streaming video youtube
Licenses: custom
Conflicts: youtube-dl
Provides: youtube-dl
Submitter: baskerville
Maintainer: disastro
Last Packager: disastro
Votes: 135
Popularity: 0.143757
First Submitted: 2012-02-27 11:10 (UTC)
Last Updated: 2021-02-24 04:53 (UTC)

Dependencies (8)

Required by (123)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »

disastro commented on 2016-04-08 15:36 (UTC)

Hello all Adopted, rewrote PKGBUILD, updated version. Wrote following community/youtube-dl, and now actually using git for source. Please report any issues that might arise, I can only test on so many systems.

xduugu commented on 2016-03-06 11:15 (UTC)

Bumping the pkgrel does not help since the pkgrel is only used when the pkgver is equal. But there are more issues with the way the package version is generated: - it can generate a different pkgver for the same commit, because it does not use the date of the commit, but the local date. - the pkgver function is run after the source was downloaded and extracted, which means that the downloaded archive is always renamed to the pkver that is given in the PKGBUILD, but this is usually not the commit that was downloaded. I think the only way for a -git package, that does not use git for downloading, is to get rid of the sources array and use curl and bsdtar manually.

flu commented on 2016-03-06 09:45 (UTC)

pkgver is date+commit hash, so your corner case could happen. The pkgver creation is not standard for a -git package because this is not (it downloads a zip snapshot). The "fix" would be adding hour, minute, even second to pkgver, but this makes the version number very long. Not a very serious issue, by the way. Any other thoughts? My suggestion is to bump the pkgrel to 2 every time on your side. Or to ignore the warning, if it is working anyway.

xduugu commented on 2016-03-05 12:40 (UTC)

Could you fix the versioning of the package? I just upgraded the package, but the new version is less than the version in the .SRCINFO file. It is actually built from a newer commit, though. Version of the AUR package: 2016.03.05.845817a-1 Date of commit: Sat, 5 Mar 2016 18:14:58 +0800 -> UTC: 2016-03-05 10:14:58 Version when built: 2016.03.05.18b0b23-1 Date of commit: Sat, 5 Mar 2016 12:14:48 +0100 -> UTC: 2016-03-05 11:14:48

RunningDroid commented on 2016-01-28 01:16 (UTC)

@yan12125 I've been having the same problems and the patch fixes things for me.

yan12125 commented on 2016-01-17 19:04 (UTC)

Sorry for the fragile LC_ALL=en_US.UTF-8 hacking. The following patch to PKGBUILD should fix all the problems. @colinkeenan @jamietanna could you check this patch works without PYTHONIOENCODING or LC_ALL tricks? diff --git a/PKGBUILD b/PKGBUILD index 0d0c88a..1ea1a28 100644 --- a/PKGBUILD +++ b/PKGBUILD @@ -29,13 +29,18 @@ pkgver() { echo $DATE.$HASH } -source=("$pkgname-$(pkgver).zip::https://github.com/rg3/$_name/archive/$_branch.zip") -sha512sums=(SKIP) +source=( + "$pkgname-$(pkgver).zip::https://github.com/rg3/$_name/archive/$_branch.zip" + 'https://github.com/yan12125/youtube-dl/commit/8ae63d1bb7f4f07529f3978da0dc4b82e67ddc62.patch' +) +sha512sums=(SKIP '8b20a4b3360b7ef48a7a4df5651026f0e97d1f11a4d1fa66ce0dc8173e87bbb9d0dbf44328dbd7fe7f6ebe742e38de4a985d5d731c537e831a1e2ef40af05b91') prepare() { cd $_name-$_branch sed -i 's|etc/bash_completion.d|share/bash-completion/completions|' setup.py sed -i 's|etc/fish/completions|share/fish/vendor_completions.d|' setup.py + + patch -Np1 -i ../8ae63d1bb7f4f07529f3978da0dc4b82e67ddc62.patch } package() {

colinkeenan commented on 2016-01-17 05:50 (UTC)

With today's update (1/16/2016), the build fails complaining about some ascii conversion, but I got it to work by adding the following to /etc/environment: PYTHONIOENCODING=utf-8

Smola commented on 2016-01-14 21:13 (UTC)

@jamietanna It's better to set it to `LC_ALL=C`.

jamietanna commented on 2016-01-14 21:04 (UTC)

Hey @flu, I've just done an upgrade, and found that the build fails on the `make` command, with the warning `/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)` if the user does not have en_US.UTF-8 installed. This may not be very common, but thought I'd document it nonetheless. I've found the following patch to work - hopefully it helps others who have the same issue. ``` diff --git a/PKGBUILD b/PKGBUILD index 8555004..93c476a 100644 --- a/PKGBUILD +++ b/PKGBUILD @@ -41,7 +41,7 @@ prepare() { package() { cd $_name-$_branch - LC_ALL=en_US.UTF-8 make bash-completion zsh-completion fish-completion README.txt youtube-dl.1 + make bash-completion zsh-completion fish-completion README.txt youtube-dl.1 python setup.py install --root="$pkgdir" --optimize=1 mv "$pkgdir"/usr/share/bash-completion/completions/youtube-dl.bash-completion \ ```

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »