Package Details: python-powerline-git 1:2.8.2+4+g82c1373b-1

Git Clone URL: https://aur.archlinux.org/python-powerline-git.git (read-only, click to copy)
Package Base: python-powerline-git
Description: The ultimate statusline/prompt utility
Upstream URL: https://github.com/powerline/powerline
Licenses: MIT
Conflicts: otf-powerline-symbols-git, powerline, powerline2, python2-powerline-git
Submitter: Lokaltog
Maintainer: gbs
Last Packager: gbs
Votes: 132
Popularity: 0.000000
First Submitted: 2013-01-23 07:28 (UTC)
Last Updated: 2021-11-14 21:19 (UTC)

Dependencies (9)

Required by (0)

Sources (1)

Latest Comments

gbs commented on 2020-11-08 19:27 (UTC)

Does anyone even use this package with python2? I'm thinking of dropping it, since it forces everyone to install it just to build this, even if one only uses the python3 version.

demizer commented on 2020-11-08 18:11 (UTC)

Changing the python2 deps to python deps seems to allow the package to build, but there are a lot of warnings.

friday13 commented on 2019-09-25 18:04 (UTC)

Errors occurred, no packages were upgraded. Command 'sudo pacman --color=always --upgrade /home/jason/.cache/pikaur/pkg/python-powerline-git-1:2.7+10+g25737d90-1-x86_64.pkg.tar.xz' failed to execute.

pizzaman commented on 2019-01-22 07:59 (UTC)

Add powerline-common to conflicts.

yitzi commented on 2018-02-21 14:21 (UTC)

What about copying all of the bindings into /usr/share/powerline/bindings for shells other then zsh?

gbs commented on 2018-01-21 13:49 (UTC)

fogine: there is no need to edit the PKGBUILD, in fact I just rebuilt it to confirm. You are possibly using a broken AUR helper which tries to install all split packages at once. If you're using plain makepkg, note that it lost its ability to select only some splitpkgs some time ago, and you need to build and then install separately.

fogine commented on 2018-01-21 11:44 (UTC) (edited on 2018-01-21 11:56 (UTC) by fogine)

This package is broken, fails with: "python2-powerline-git and python-powerline-git are in conflict" It's trying to install both versions at the same time...

EDIT: I see... You are supposed to choose your own version by editing PKGBUILD... I installed this package over the years quite few times... and this always gets me... Should be clearly stated in the docs

gbs commented on 2017-11-01 16:22 (UTC)

fedex_cain: package updated, thanks for reminding me to push my changes.

fedex_cain commented on 2017-10-22 12:28 (UTC)

Hey, the powerline project contains a systemd service file for the powerline-daemon (located in powerline/dist/sytemd/powerline-daemon.service). Can you add it to be installed by this package?

0x647262 commented on 2017-02-04 02:57 (UTC) (edited on 2017-02-04 20:31 (UTC) by 0x647262)

abydos62: https://wiki.archlinux.org/index.php/GnuPG Also, when are you getting that message?

abydos62 commented on 2017-01-20 02:53 (UTC)

Hey, I'm getting this error message: error: python2-setuptools: signature from "Felix Yan <felixonmars@gmail.com>" is invalid :: File /var/cache/pacman/pkg/python2-setuptools-1:33.0.0-1-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)). Let me know if its an issue on your end, or if there is a solution available.

bartus commented on 2017-01-09 16:08 (UTC) (edited on 2017-01-09 16:14 (UTC) by bartus)

@j1simon There is no need to update this package - it's properly formatted. According to https://www.archlinux.org/pacman/PKGBUILD.5.html#_package_splitting Problem lies in AUR helpers which _in my opinion_ should build packages in chroot instead of dumping all build_depends on the root system.

j1simon commented on 2016-12-27 10:59 (UTC) (edited on 2016-12-27 11:11 (UTC) by j1simon)

Is this package actually maintained? I think is a very bad idea mix in same package Powerline for python 2 and 3. It doesn't compile: "python2-powerline-git and python-powerline-git are in conflict". The AUR system doesn't support this mix. For this package, it isn't necessary 'python2-setuptools' nor 'python2-sphinx'. It should be: 'python-sphinx' and change 'make man SPHINXBUILD=sphinx-build2' by 'make man SPHINXBUILD=sphinx-build'.

Daqu commented on 2016-10-22 10:21 (UTC)

@hiddenhand I encountered the same problem.The solution @ahaqxjl commented on 2016-05-20 09:09 done!

ahaqxjl commented on 2016-05-20 09:09 (UTC)

@n1lo you can install only python-powerline-git via: Edit PKGBUILD? Select Y, then enter your favored editor such as vim Delete 'python2-powerline-git' from the pkgname, then save and continue.

wcasanova commented on 2016-04-27 16:09 (UTC) (edited on 2016-04-27 16:09 (UTC) by wcasanova)

vim to work add in ~.vimrc let $PYTHONPATH='/usr/lib/python3.5/site-packages' set laststatus=2

Siosm commented on 2016-04-18 14:50 (UTC)

Unfortunately I won't be the one to rebase this package on the official one as it would take quite some time to do so properly and I've just realized that don't use the git version anymore. Thus I'm orphaning this package.

Siosm commented on 2016-04-18 14:09 (UTC)

@n1lo, @hiddenhand: Again, you don't need to install both python2 and python3 packages for it to work. Just install the version you need. As powerline is available in the official repository I will rebase this version against it and thus you may be able to install both at the same time.

n1lo commented on 2016-02-23 15:50 (UTC)

@hiddenhand I've give up on this and install python-powerline only.

hiddenhand commented on 2016-02-23 13:04 (UTC)

@n1lo have you found a way to fix this?? I'm still encountering that conflicting error

Siosm commented on 2016-01-18 09:16 (UTC)

@Fedaykin, @lucc: Please use the '−A' or '−−ignorearch' option with your package builder/manager (makepkg/yaourt/...).

lucc commented on 2016-01-18 08:55 (UTC)

And armv6h, thank you.

Fedaykin commented on 2015-11-23 23:13 (UTC)

you can add 'armv7h' to arch in PKGBUILD

Siosm commented on 2015-08-03 06:14 (UTC)

@n1lo: Then try installing only python-powerline-git.

n1lo commented on 2015-08-02 23:56 (UTC)

@Siosm I don't know. I tried to install and got this error. I just need support for python 3 not 2.

Siosm commented on 2015-08-02 17:59 (UTC)

@n1lo: Is there a use-case requiring both versions to be installed at the same time?

n1lo commented on 2015-07-31 17:47 (UTC)

loading packages... resolving dependencies... looking for conflicting packages... error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: python2-powerline-git and python-powerline-git are in conflict

eigengrau commented on 2015-07-21 11:28 (UTC)

Cheers!

Siosm commented on 2015-07-20 20:07 (UTC)

@eigengrau: Good catch. This should be fixed now.

eigengrau commented on 2015-07-20 18:49 (UTC)

The build currently fails when building only for Python 3 («makepkg --pkg python-powerline-git») when python2-sphinx is not installed. The first «make man» will fail, and since «build()» is run with the option «errexit», the whole build then fails.

Fedaykin commented on 2015-04-27 00:42 (UTC)

when doing source /usr/lib/python3.4/site-packages/powerline/bindings/zsh/powerline.zsh I'm not getting anything (powerline for VIM works fine)

Firef0x commented on 2015-04-08 21:25 (UTC)

Why is this package flagged out-of-date? Just because the pkgver is 0.0.0?

Firef0x commented on 2014-12-20 18:22 (UTC)

Hello, @pablox ! Since the upstream URL is changed from https://github.com/Lokaltog/powerline to https://github.com/powerline/powerline , though the old one would redirect to the new one, I think it's good to update the PKGBUILD and point to the new address. And it's time to submit your first commit since adopted. Hope for your reply! Yours sincerely!

pablox commented on 2014-11-15 23:34 (UTC)

¬_¬. You weren't showing status bar at all... this wasn't a python-powerline issue xD. Well, I'm glad you sort it out :)

fixles commented on 2014-11-15 17:13 (UTC)

Ok so after a lot of reading I worked it out. I needed to add two lines to my vimrc let $PYTHONPATH='/usr/lib/python3.4/site-packages' set laststatus=2 The last one set laststatus=2 is what actually makes powerline show up. I'm using urxvt so I needed to install otf-inconsolata-powerline-git from the AUR and add the following line to my .Xdefaults. urxvt*font: xft:Monospace:size=11,xft:Inconsolata for Powerline:pixelsize=20

fixles commented on 2014-11-15 02:28 (UTC)

When I type echo $PYTHONPATH its blank. When I export PYTHONPATH='/usr/lib/python3.4/site-packages' vim opens fine but no bar I tried moving my .bashrc and .vimrc but still nothing. I've just rebuilt the package again and still doesnt work. Am i missing a dependency or something? Would really like to get this to work.

pablox commented on 2014-11-11 00:09 (UTC)

Could it be that you have the $PYTHONPATH variable exported somewhere else, or that you have another python runtime installed?

fixles commented on 2014-11-10 23:09 (UTC)

@pablox Thanks that stopped the error but just get the default vim line at the bottom?

pablox commented on 2014-11-10 00:20 (UTC)

Add the following: let $PYTHONPATH='/usr/lib/python3.4/site-packages' in your .vimrc file. That should do it.

fixles commented on 2014-11-09 23:22 (UTC)

Didnt work for me >>> ~ vim .Xdefaults Traceback (most recent call last): File "<string>", line 9, in <module> ImportError: No module named powerline.vim An error occurred while importing powerline module. This could be caused by invalid sys.path setting, or by an incompatible Python version (powerline requires Python 2.6, 2.7 or 3.2 and later to work). Please consult the troubleshooting section in the documentation for possible solutions. Unable to import powerline, is it installed? Press ENTER or type command to continue

7kry commented on 2014-10-20 05:06 (UTC)

To use battery module, `upower' seems to be required. Then I think optdepends should include `upower'.

Lokaltog commented on 2014-10-15 10:25 (UTC)

There's been *a lot* of updates since the last PKGBUILD update. Please search the GitHub issue tracker at https://github.com/Lokaltog/powerline/issues, and report any issues there as I'm not currently contributing to Powerline development. I think you have to update your config file, as it appears several backwards-incompatible changes have been introduced since the previous PKGBUILD update. See https://github.com/Lokaltog/powerline/issues/995 and https://github.com/Lokaltog/powerline/issues/1054 for similar issues. Also try running powerline-lint to debug your config files.

qifei9 commented on 2014-10-15 10:19 (UTC)

After this update, powerline does not work for me. Get many errors like : 2014-10-15 12:02:41,925:ERROR:vim:matcher_generator:Failed to import attr nerdtree from module powerline.matchers.plugin.nerdtree: No module named 'powerline.matchers.plugin' Traceback (most recent call last): File "/usr/lib/python3.4/site-packages/powerline/__init__.py", line 315, in get_module_attr return getattr(__import__(module, fromlist=(attr,)), attr) ImportError: No module named 'powerline.matchers.plugin' ... 2014-10-15 12:02:41,989:ERROR:vim:segment_generator:Failed to generate segment from {'name': 'virtcol_current', 'priority': 20, 'draw_soft_divider': False, 'before': ':', 'width': 3, 'align': 'l'}: 'function' Traceback (most recent call last): File "/usr/lib/python3.4/site-packages/powerline/segment.py", line 298, in get contents, _contents_func, module, function_name, name = get_segment_info(data, segment) File "/usr/lib/python3.4/site-packages/powerline/segment.py", line 62, in get_function function_name = segment['function'] KeyError: 'function'

x4fyr commented on 2014-07-24 12:55 (UTC)

Why is the i3 and awesome support missing?

FernandoBasso commented on 2014-04-27 13:01 (UTC)

I had to export PYTHONPATH=/usr/lib/python3.4/site-packages Not that it is 3.4, not 3.3. It worked for me.

freestyler7 commented on 2014-04-04 22:03 (UTC)

fontconfig is required for the commands in .install script to work and also the "export PYTHONPATH=/usr/lib/python3.3/site-packages" needs updating for python 3.4.

Lokaltog commented on 2014-03-28 18:30 (UTC)

Unfortunately yes. Python 3 support usually isn't built with vim, and I think this package should be available as long as we support Python 2. I'd like to ditch Python 2 completely as well, but I don't think that can happen for another couple of years.

Lokaltog commented on 2014-03-28 18:27 (UTC)

The font provided in this package only includes the glyphs, and works as a fallback for *any* font, so in many cases it's not necessary to use a patched font. I'm not sure how other powerline font packages conflict with this one, if they use https://github.com/Lokaltog/powerline-fonts as a source then PowerlineSymbols.otf shouldn't be included. If the fallback font is included in other packages anyways, they should remove it, as the fallback font only includes the powerline glyphs and shouldn't be part of a group of full fonts.

Svenstaro commented on 2014-03-28 16:25 (UTC)

Is there any merit in keeping this package around? Why not Python 3?

Svenstaro commented on 2014-03-28 16:18 (UTC)

You should most probably not provide the fonts in this package. The fonts are in another repository. This should optdept on the fonts package at best. Currently the fonts package is in file conflict with this one and that's rather bad.

swiftscythe commented on 2014-01-29 21:22 (UTC)

I managed to get the symbols without the weird characters by removing the lines that install the fonts in this PKGBUILD and installing a powerline-patched font from the AUR

Lokaltog commented on 2014-01-23 07:20 (UTC)

Yes, you need set laststatus=2 to show any statusline in vim. It's a common setting and not a "hack" or anything like that. :)

lelele commented on 2014-01-23 02:32 (UTC)

Couldn't get powerline to work in VIM, so I use the one suggested here: https://github.com/Lokaltog/powerline/issues/521#issuecomment-18847799; set laststatus=2. It worked. Is this really the proper step to do this? Did I do something wrong with my VIM setup?

Lokaltog commented on 2014-01-19 10:55 (UTC)

I've updated the packages, sorry about the delay.

fazo96 commented on 2013-12-22 16:28 (UTC)

May I suggest fixing the package so it can be installed using AUR helpers such as Aura? Nice work btw.

kh3phr3n commented on 2013-12-09 11:40 (UTC)

Hi, Same here, everything is ok in Konsole but "nbsp" problem with gVim. Issue: https://github.com/Lokaltog/powerline/issues/698 Wait & See :)

swiftscythe commented on 2013-12-04 19:47 (UTC)

Hi! I can't get the symbols from the powerline-fonts in gVim (however it works as expected in Vim...) Any one else having this problem? Did I miss something? Thanks :)

t0m5k1 commented on 2013-11-10 21:50 (UTC)

pacaur -u python2-powerline-git :: Starting AUR upgrade... :: resolving dependencies... :: Could not read python2-powerline-git PKGBUILD: badly packaged tarball unsure how to resolve this??

Stalafin commented on 2013-10-26 11:55 (UTC)

Because vim has issues finding powerline; in power.install, it is suggested to set: > export PYTHONPATH=/usr/lib/python3.3/site-packages This can however mess up python2, which still many applications rely on, because PYTHONPATH is used for both python2 and python3 (very silly, but that's what it is). Because many people just use powerline for vim, I suggest adding gnomeye's comment [1] to the installation info of the PKGBUILD: > add “ let $PYTHONPATH="/usr/lib/python3.3/site-packages" ” to .vimrc 1: https://github.com/Lokaltog/powerline/issues/298#issuecomment-15633045

fridsun commented on 2013-10-14 19:04 (UTC)

I would recommend splitting powerline and powerline font solution install since fontconfig isn't a universal method. Btw I am having uberben's error even though I don't have airline. I had it once but removed it.

fridsun commented on 2013-10-14 18:27 (UTC)

Beware that you may encounter errors if you have installed other powerline fontconfig packages before this.

Lokaltog commented on 2013-09-27 22:01 (UTC)

Those docs are for another project.

hav3lock commented on 2013-09-26 23:11 (UTC)

Also, this package cannot be installed with Aura, pacaur, or spinach. Please fix this.

hav3lock commented on 2013-09-26 23:11 (UTC)

Also, this package cannot be installed with Aura, pacaur, or spinach. Please fix this.

hav3lock commented on 2013-09-26 23:07 (UTC)

Please add the vim documentation to the package, you can get it here: https://github.com/Lokaltog/vim-powerline/blob/develop/doc/Powerline.txt

hav3lock commented on 2013-09-26 23:00 (UTC)

Please add the vim documentation to the package, you can get it here: https://github.com/Lokaltog/vim-powerline/blob/develop/doc/Powerline.txt

jck commented on 2013-09-16 23:59 (UTC)

distribute needs to be replaced by setuptools

commented on 2013-09-11 12:52 (UTC)

After the latest update I keep having this error chown: cannot access '/var/cache/pacman/pkg/python2-powerline-git20032/python2-powerline-git': No such file or directory

Lokaltog commented on 2013-08-27 07:45 (UTC)

Ah, I see. Anyways, as a temporary workaround you can delete /usr/share/vim/vimfiles/plugin/powerline.vim to disable Powerline globally.

uberben commented on 2013-08-26 15:51 (UTC)

I've been trying out the spf13 vim configuration, which aims to be pretty independent (ie. no external dependencies on things like python) and so it uses airline instead of powerline. I've used both and they are both great, but I like the portability of a viml version. This is the error I get when powerline for vim is enabled (I'm running python 3.3.2): An error occurred while importing the Powerline package. This could be caused by an invalid sys.path setting, or by an incompatible Python version (Powerline requires Python 2.6+ or 3.2+ to work). Please consult the troubleshooting section in the documentation for possible solutions. Press ENTER or type command to continue

Lokaltog commented on 2013-08-23 16:16 (UTC)

Hm, I didn't really think about that. I'll see what I can do. Is there a particular reason why you want to use Powerline for tmux, but not in vim? Also, what kind of error do you get when using Powerline and airline together?

uberben commented on 2013-08-23 14:54 (UTC)

It would be nice if this package didn't enable powerline by default. I installed this just for tmux, but I get errors when I launch vim because powerline for vim is enabled by default. I use vim-airline instead, so I don't need powerline for vim. I'm not sure the best way to change the PKGBUILD for general use, though.

Lokaltog commented on 2013-07-31 13:54 (UTC)

The build error has been fixed in the latest revision.

0X1A commented on 2013-07-26 08:37 (UTC)

Getting failed build: File "setup.py", line 11, in <module> README = open(os.path.join(here, 'README.rst')).read() File "/usr/lib/python3.3/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 40: ordinal not in range(128)

ndt commented on 2013-06-30 03:10 (UTC)

@demil133 I was surprised. Taking a look at the PKGBUILD for vim (Which is the same as the one for vim, suprisingly: https://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/vim ) it sets the following: --enable-pythoninterp \ --disable-python3interp \ I changed --disable there to --enable, built the package, and it worked. I have a custom PKGBUILD to do this now, but the AUR won't let me upload it because it is a bundle of packages.

commented on 2013-06-29 00:40 (UTC)

@ndt: It's on the requirements, I think. You can, instead of compiling it yourself, just install gvim. It comes with the "huge" flag, which includes almost everything.

ndt commented on 2013-06-28 23:49 (UTC)

Do you have to compile Vim with python3 support for this to work in Vim? For me, Powerline for Vim crashed until I did that with this package.

HalosGhost commented on 2013-06-28 15:55 (UTC)

I added some quick pull requests to further clean up the package function. All the best,

Lokaltog commented on 2013-06-28 12:16 (UTC)

The package has been updated to use the new VCS syntax. Let me know if you have any issues with the new PKGBUILD.

Lokaltog commented on 2013-06-21 22:58 (UTC)

I've read the comment. I'll update it as soon as I have time to review and test the PKGBUILD.

onny commented on 2013-06-20 19:33 (UTC)

Please upgrade your PKGBUILD according to @arielp hint.

arielp commented on 2013-05-25 18:09 (UTC)

I've been using this one for a while. It seems to work OK. http://ix.io/5N9

Lokaltog commented on 2013-05-06 13:50 (UTC)

Thanks for the contribution! I'll look at it asap.

HalosGhost commented on 2013-05-02 20:44 (UTC)

Have you looked into updating this PKGBUILD for the new VCS syntax? It should clean it up quite a bit. I may end up installing this shortly, and if I do, I can probably provide the updated PKGBUILD if you would like.

commented on 2013-04-23 15:57 (UTC)

@ Lokaltog For awesome-wm, I followed these steps successfully: https://powerline.readthedocs.org/en/latest/overview.html#awesome-widget However, I am having great difficulties getting started on adding little widgets on that bar to make it look like that. What does the default look like? Is there a template I can look at and/or work off of? If I can get it to work I would definitely write system info. ----- I managed to fix that error, now I'm into customizing the vim part of it.

Lokaltog commented on 2013-04-23 07:54 (UTC)

@3xOSC It's certainly possible to create a similar theme for Awesome, but it's currently not provided in Powerline. The default theme is simpler, but please feel free to write a couple of system info segments if you can. Regarding the error you're receiving, it is most likely an issue with your Python package search path. I've personally never experienced this issue, but several users have reported that updating your PYTHONPATH as mentioned in the post-install docs will resolve this issue: export PYTHONPATH=/usr/lib/python3.3/site-packages

cgirard commented on 2013-04-22 16:20 (UTC)

Yeah I am sorry I thought it was written there. It is in post install of this PKGBUILD anyway.

commented on 2013-04-22 16:13 (UTC)

I *did* look at the troubleshooting section right here: https://powerline.readthedocs.org/en/latest/installation/linux.html#i-get-e858-e860-error-in-vim-eval-did-not-return-a-valid-python-object you wanna read it out loud to me?

cgirard commented on 2013-04-22 15:52 (UTC)

Well, just do what is told: "Please consult the troubleshooting section in the documentation for possible solutions." You will need to define PYTHONPATH (alternatively use python2-powerline-git).

commented on 2013-04-22 15:39 (UTC)

Any one know why I get this error? An error occurred while importing the Powerline package. This could be caused by an invalid sys.path setting, or by an incompatible Python version (Powerline requires Python 2.6+ or 3.2+ to work). Please consult the troubleshooting section in the documentation for possible solutions. Press ENTER or type command to continue

commented on 2013-04-22 14:38 (UTC)

Is it possible to use this python powerline to achieve this look on awesome? https://github.com/romockee/powerarrow The reason why I ask was because of this: https://powerline.readthedocs.org/en/latest/overview.html?highlight=awesome

Lokaltog commented on 2013-04-12 18:34 (UTC)

Allright, I've updated with gvim as an optdepends and added python2-powerline-git to conflicts. I'll add the extra optdepends (tmux, bash, etc.) later.

cgirard commented on 2013-04-12 18:17 (UTC)

Yes seems the right thing to do. You could add tmux as well.

Lokaltog commented on 2013-04-12 18:13 (UTC)

Thanks, I'll add it as an optdepends, since Powerline itself doesn't require vim or gvim.

cgirard commented on 2013-04-12 17:48 (UTC)

gvim package provides vim but is compiled with more dependencies than vim package. I was using the python3 version and switched to python2 as the python3 version need to set PYTHONPATH which cause a lot problem with python2 apps.

jakob commented on 2013-04-12 17:45 (UTC)

Is there any advantage of using the python3 version over the python2 one? Ist the comment by flying-sheep relevant if I mainly use vim but have gvim installed (since I need the --server capability anyway)?

flying-sheep commented on 2013-04-10 15:31 (UTC)

hi, you should add gvim to the dependencies, as plain vim on arch isn’t compiled with python support!

cgirard commented on 2013-03-19 12:20 (UTC)

@bitcrusher: I had the same error. I am not sure what caused this but relaunching makepkg was enough to solve this for me. @hexchain: just wondering, what is the use case of simultaneous use of python-powerline-git and python2-powerline-git?

hexchain commented on 2013-03-16 09:02 (UTC)

This package conflicts with python2-powerline-git. Maybe it's a better idea to split the package into {vim,bash,tmux,zsh,python,python2}-powerline?

bitcrusher commented on 2013-03-15 23:14 (UTC)

Traceback (most recent call last): File "setup.py", line 11, in <module> README = open(os.path.join(here, 'README.rst')).read() File "/usr/lib/python3.3/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 40: ordinal not in range(128) What is the issue here?

Lokaltog commented on 2013-03-12 11:38 (UTC)

Sure. I don't have that path on my system and other OTF fonts have been installed in TTF/ so I assumed it was the standard. I'll change it.

kuroneko commented on 2013-03-12 00:29 (UTC)

Can you move the font to be installed in OTF/ instead of TTF/?

Lokaltog commented on 2013-03-08 17:07 (UTC)

The PKGBUILD and license has been updated. Thanks for your comments.

Lokaltog commented on 2013-03-04 15:36 (UTC)

Thanks for the comments, I'll look into this asap.

cgirard commented on 2013-03-04 14:42 (UTC)

I'm not sure why you set pkgbase. It makes "makepkg -S" generate the files in a python-powerline directory instead of python-powerline-git. This is not standard PKGBUILD behavior and results in malfunction with AUR helpers.

jsteel commented on 2013-02-28 12:52 (UTC)

vim-powerline-git has merged with this package, I suggest adding that to replaces.

Profpatsch commented on 2013-02-21 22:36 (UTC)

With the python2 version I got a lot of “eval did not return a valid python object”, but with this I get “An error occured while importing the Powerline package. This could be caused by an invalid sys.path setting, or by an incompatible Python version (Powerline requires Python 2.7 or 3.3+ to work). Please consult the troubleshooting section in the documentation for possible solutions.” All packages are their newest versions. I’ll try installing it via Vundle next.

lowfatcomputing commented on 2013-02-21 02:56 (UTC)

I needed to add: export PYTHONPATH=/usr/lib/python3.3/site-packages to my /etc/profile for vim.

Lokaltog commented on 2013-02-07 21:43 (UTC)

Thanks, I changed the installation method but forgot to update the PKGBUILD. I'll fix it tomorrow morning.

commented on 2013-02-07 21:24 (UTC)

Sorry for the incomplete comment, line 53 should change to: install -m644 "powerline/bindings/vim/plugin/powerline.vim" "${pkgdir}/usr/share/vim/vimfiles/plugin/powerline.vim"

commented on 2013-02-07 21:12 (UTC)

-> Installing fonts... -> Installing vim plugin... install: cannot stat ‘powerline/bindings/vim/powerline.vim’: No such file or directory ==> ERROR: A failure occurred in build().

Lokaltog commented on 2013-02-05 13:18 (UTC)

The package checks for Python support if it's installed with e.g. Vundle or without user intervention (see bindings/vim/plugin/source_plugin.vim). But I forgot that the plugin file that's installed with this package doesn't include this check. I don't really think it's an issue, but if it becomes an issue I'll consider including this check in the other plugin file as well (or simply change which plugin file gets installed with this package).

pablox commented on 2013-02-05 02:30 (UTC)

The package never checks for vim python support built on the vim binary. Shouldn't be there on the powerline.vim some: if has('python') || ('python3') blabla endif ¿? Or it's just assumed because the vim package includes it by default?

Lokaltog commented on 2013-01-24 06:59 (UTC)

Thanks, I'll fix it in a moment.

commented on 2013-01-23 23:38 (UTC)

FYI, the PKGBUILD probably wants a "conflicts=('powerline-git')" for people just coming from the old package. As is, pacman doesn't know to uninstall the previous and complains about files already existing in the filesystem.