Package Details: ranger-git

Git Clone URL: (read-only)
Package Base: ranger-git
Description: A simple, vim-like file manager.
Upstream URL:
Licenses: GPL
Conflicts: ranger
Provides: ranger
Submitter: None
Maintainer: aksr
Last Packager: aksr
Votes: 136
Popularity: 0.150552
First Submitted: 2010-03-13 02:08
Last Updated: 2018-03-24 06:34

Dependencies (13)

Required by (8)

Sources (1)

Latest Comments

FichteFoll commented on 2017-07-05 19:48

The repo has moved to (from hut/ranger). PKGBUILD still works though.

nfnty commented on 2017-02-09 13:33

@ansatz It's been fixed upstream.

ansatz commented on 2017-02-09 11:27

Building fails:

==> Making package: ranger-git (Thu 9 Feb 13:26:45 EET 2017)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Cloning ranger-git git repo...
Cloning into bare repository '/tmp/ranger-git/ranger-git'...
remote: Counting objects: 25871, done.
remote: Compressing objects: 100% (38/38), done.
remote: Total 25871 (delta 14), reused 0 (delta 0), pack-reused 25833
Receiving objects: 100% (25871/25871), 7.55 MiB | 278.00 KiB/s, done.
Resolving deltas: 100% (16411/16411), done.
==> Validating source files with md5sums...
ranger-git ... Skipped
==> Extracting sources...
-> Creating working copy of ranger git repo...
Cloning into 'ranger-git'...
==> Starting pkgver()...
==> Updated version: ranger-git
==> Entering fakeroot environment...
==> Starting package()...
error: package directory 'ranger/ext/vcsranger/gui' does not exist
==> ERROR: A failure occurred in package().

rscholer commented on 2015-10-04 22:02

I get the following error when running makepkg:
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Using "", fixes this.

nfnty commented on 2014-10-04 00:11

Please add this to the PKGBUILD:

'file: for determining file types'
'python-chardet: in case of encoding detection problems'
'sudo: to use the "run as root"-feature'
'libcaca: for ASCII-art image previews'
'highlight: for syntax highlighting of code'
'atool: for previews of archives'
'w3m: for previews of images and html pages'
'lynx: for previews of html pages'
'elinks: for previews of html pages'
'poppler: for pdf previews'
'transmission-cli: for viewing bittorrent information'
'mediainfo: for viewing information about media files'
'perl-image-exiftool: for viewing information about media files'

hut commented on 2014-08-16 14:35

What metadata is bad? The version number?

bchretien commented on 2014-08-16 14:09

This could simply be reuploaded with the appropriate metadata (e.g. use mkaurball from pkgbuild-introspection).

markfoxwell commented on 2014-04-21 20:09

Is there any reason this is still flagged as out-of-date?

hut commented on 2013-04-08 20:59

Good, since pacman 4.1 is in core, I'm gonna update the pkgbuild. Thank you for doing the conversion! ^_^

Anonymous comment on 2013-04-08 20:24

Well, as far as I know Arch users should always be up to date and since pacman 4.1 is in [core], we don't need to take care of pacman 4.0.3 anymore. But of course you can wait with the update, since the old build still works (but the pkgver won't be updated then).

hut commented on 2013-04-08 19:48

It doesn't seem to work with pacman 4.0.3 out of the box though :S
==> ERROR: There is no agent set up to handle git+git URLs. Check /etc/makepkg.conf.

So I'm not sure if I should upgrade the pkgbuild yet or not.

Anonymous comment on 2013-04-08 10:36

Hey hut! In case you're interested, I've created a PKGBUILD for ranger-git, which supports pacman 4.1. If you like it, feel free to use it.

atweiden commented on 2012-05-13 22:34

@everyone wanting Ranger with Python2 and official GitHub source, see:

Anonymous comment on 2011-08-30 07:48

@mkaito, ranger depends on "Python 2.6 or Python 3.1 with the curses module", so the user can chose between both. However, since python3 is the chosen default on Archlinux, it's best to use this one in the default PKGBUILD. You can always edit it to your liking and do a sed 's/python/python2/g' -i PKGBUILD as mentioned in the post befor yours. I also use ranger with python2.

mkaito commented on 2011-08-30 02:43

Development seems to have moved to github (, and the PKGBUILD needs to be updated to use python2 instead of python.

andmars commented on 2011-02-27 10:23

since there are currently some problems with python (ranger can't open external programs for .jpg, .pdf, etc.)
as a workaround edit this PKGBUILD with;

sed 's/python/python2/g' -i PKGBUILD

going back to python2. that way it works just fine again.

as found here;

hut commented on 2010-10-19 15:20

why? it works with python3 too.
To use python2 again, you can change the "python" line to "python2.6"

hut commented on 2010-10-19 15:20

why? it works with python3 too.
To use python2 again, you can change the "python" line to "python2.6"

hut commented on 2010-10-19 15:20

why? it works with python3 too.
To use python2 again, you can change the "python" line to "python2.6"

Anonymous comment on 2010-10-19 15:15

Yes, I see now that it works. But it does have to be rebuilt after the python change.

Anonymous comment on 2010-10-19 15:13

Exactly, all instances of "python" in the PKGBUILD should be changed to "python2".

hut commented on 2010-10-19 15:06

why? it works with python3 too.
To use python2 again, you can change the "python" line to "python2.6"

Anonymous comment on 2010-10-19 14:45

Python is now python 3, so the package needs to be modified.

Anonymous comment on 2010-09-08 06:39

Thank you very much for packaging this!