Package Details: polybar 3.3.1-2

Git Clone URL: https://aur.archlinux.org/polybar.git (read-only)
Package Base: polybar
Description: A fast and easy-to-use status bar
Upstream URL: https://github.com/polybar/polybar
Keywords: bar bspwm i3 lemonbar lemonbuddy polybar
Licenses: MIT
Conflicts: polybar-git
Submitter: jaagr
Maintainer: jaagr (NBonaparte, patrick96)
Last Packager: patrick96
Votes: 191
Popularity: 13.267440
First Submitted: 2016-11-19 05:09
Last Updated: 2019-06-23 19:24

Dependencies (21)

Required by (2)

Sources (1)

Pinned Comments

TheGreatAndyChow commented on 2019-04-23 03:46

For problems with conda, simply "conda deactivate", it will install. No need to purge path or remove anaconda.

Latest Comments

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

Chais commented on 2018-03-14 21:42

On that note, would you consider adding alsa-lib, libmpdclient, wireless_tools, jsoncpp and curl as makedepends? They have to be present at build time for the modules to work and when building in a container or chroot that's the way to ensure that the optdepends actually work.

Even when building directly on the target machine the current PKGBUILD requires the user to install the desired optdepends before compiling the package, which is rather counter-intuitive for optdepends.

Chais commented on 2018-03-13 01:20

@patrick96 I usually update with

TMPDIR=/tmp aursync -cuT --no-view

so it builds in a container.

patrick96 commented on 2018-03-12 21:05

@Chais: I think this is caused by aurutils calling git rev-parse on the aur repo. The repo with the PKGBUILD probably didn't get updated properly and somehow ended up in detached HEAD mode. This looks like an aurbuild issue, what command did you use?

Chais commented on 2018-03-12 15:18

With aurutils I have the problem that I get the following error when updating the package:

fatal: HEAD does not point to a branch

But only when updating. Not when I delete the directory and the repo is downloaded anew. Not sure if this is problem with aurutils, makepkg or the PKGBUILD.

patrick96 commented on 2018-03-12 07:20

@darm use the latest PKGBUILD do a clean build. We pushed a fix for that yesterday

darm commented on 2018-03-12 07:09

Latest build is failing for me when linking cxx static library libxpp.a with the following message:

Scanning dependencies of target xpp
[  1%] Linking CXX static library libxpp.a
Traceback (most recent call last):
  File "/home/darm/.cache/pacaur/polybar/src/polybar/lib/xpp/generators/cpp_client.py", line 3163, in <module>
    from xcbgen.state import Module
  File "/usr/lib/python3.6/site-packages/xcbgen/state.py", line 7, in <module>
    from xcbgen import matcher
  File "/usr/lib/python3.6/site-packages/xcbgen/matcher.py", line 12, in <module>
    from xcbgen.xtypes import *
  File "/usr/lib/python3.6/site-packages/xcbgen/xtypes.py", line 1221, in <module>
    class EventStruct(Union):
  File "/usr/lib/python3.6/site-packages/xcbgen/xtypes.py", line 1239, in EventStruct
    out = __main__.output['eventstruct']
KeyError: 'eventstruct'
make[2]: *** [lib/xpp/CMakeFiles/xpp.dir/build.make:70: lib/xpp/libxpp.a] Error 1
make[1]: *** [CMakeFiles/Makefile2:403: lib/xpp/CMakeFiles/xpp.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
:: failed to build polybar package(s)

patrick96 commented on 2018-03-04 10:40

You got it. I always forget that

RemoteAdmin commented on 2018-03-04 10:05

Would you mind updating the .SRCINFO? Your last update 2017-12-04 didn't include it

patrick96 commented on 2018-02-02 07:38

@TheSilentDrifter See https://github.com/jaagr/polybar/wiki/Known-Issues

TheSilentDrifter commented on 2018-02-01 21:29

There is currently a broken symbolic link with libjsoncpp.so.19 now that it has been updated to be libjsoncpp.so.20