Package Details: polybar-git 3.7.2-1

Git Clone URL: https://aur.archlinux.org/polybar-git.git (read-only, click to copy)
Package Base: polybar-git
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
Provides: polybar
Submitter: jaagr
Maintainer: jaagr (NBonaparte, patrick96)
Last Packager: patrick96
Votes: 55
Popularity: 0.34
First Submitted: 2016-11-19 05:07 (UTC)
Last Updated: 2024-08-17 11:53 (UTC)

Required by (11)

Sources (1)

Pinned Comments

patrick96 commented on 2021-12-28 15:29 (UTC)

I went ahead and added aarch64 as an architecture to the PKGBUILD.

Please be aware that polybar is not maintained on aarch64 and there is no official support for it (even if it will probably run fine). We do our best to get it to compile on ARM and do accept patches for that, but for any ARM-related runtime issues we cannot provide proper support because we don't have access to aarch64 machines.

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

jameh commented on 2020-05-17 00:55 (UTC) (edited on 2020-05-17 00:59 (UTC) by jameh)

ah - I realized that polybar -vvv doesn't use the proper release number, but g5cd7295a is indeed the latest commit... EDIT: gotcha - looking forward to 3.5 :D

patrick96 commented on 2020-05-17 00:55 (UTC)

@jameh That's how non-release commits are versioned unfortunately. 3.4.0-106-g5cd7295a is newer than 3.4.3. The master branch where git describe gets the version information doesn't know about patch releases (3.4.X), it only knows about minor releases (3.X.0).

But we want to adapt a different branching scheme in 3.5.0, so that this doesn't happen anymore.

jameh commented on 2020-05-17 00:34 (UTC)

I feel like I might be messing something up, but this only installs 3.4.0-106-g5cd7295a for me which is out-of-date. Looking at the PKGBUILD, git -C polybar describe --long --tags returns 3.4.0-106-g5cd7295a whereas git -C polybar log shows the most recent commits. (We're past 3.4.3 now)

patrick96 commented on 2020-01-31 06:14 (UTC)

@milk Thanks, fixed

milkii commented on 2020-01-30 23:28 (UTC)

polybar-git currently fails when make with mkchrootpkg / testing-x86_64-build

-- Configuring done
-- Generating done
-- Build files have been written to: /build/polybar-git/src/polybar/build
Scanning dependencies of target doc_html
[  1%] sphinx-build html: see doc/builder-html.log
WARNING: html_static_path entry '/build/polybar-git/src/polybar/doc/_static' does not exist
[  1%] Built target doc_html
Scanning dependencies of target doc_man
[  2%] sphinx-build man: see doc/builder-man.log
WARNING: html_static_path entry '/build/polybar-git/src/polybar/doc/_static' does not exist
[  2%] Built target doc_man
Scanning dependencies of target doc
[  2%] Built target doc
[  3%] Generating ../../../lib/xpp/include/xpp/proto/x.hpp
Traceback (most recent call last):
  File "/build/polybar-git/src/polybar/lib/xpp/generators/cpp_client.py", line 3193, in <module>
    module.generate()
  File "/usr/lib/python3.8/site-packages/xcbgen/state.py", line 126, in generate
    item.out(name)
  File "/build/polybar-git/src/polybar/lib/xpp/generators/cpp_client.py", line 3007, in cpp_event
    cpp_event = CppEvent(self.opcodes[name], opcode, c_name, _ns, name, self.fields)
  File "/build/polybar-git/src/polybar/lib/xpp/generators/cppevent.py", line 207, in __init__
    for name in self.names[0:-1]:
TypeError: 'map' object is not subscriptable
make[2]: *** [lib/xpp/CMakeFiles/xpp.dir/build.make:74: ../lib/xpp/include/xpp/proto/x.hpp] Error 1
make[2]: *** Deleting file '../lib/xpp/include/xpp/proto/x.hpp'
make[1]: *** [CMakeFiles/Makefile2:521: lib/xpp/CMakeFiles/xpp.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
==> ERROR: A failure occurred in build().

patrick96 commented on 2019-10-05 14:42 (UTC)

@nicocot best ask the pamac people. But generally removing the build directory pamac used for polybar should force pamac to recompile

nicocot commented on 2019-10-05 14:36 (UTC)

@patrick96 I'm using pamac-manager and I don't know how to recompile with this package manager. I removed and reinstalled the polybar-git package several times with pamac-manager, without success.

patrick96 commented on 2019-10-05 14:30 (UTC)

@nicocot Please only use the symlink method as a last resort when you can't recompile. It could potentially break other programs.

nicocot commented on 2019-10-05 14:29 (UTC) (edited on 2019-10-05 14:30 (UTC) by nicocot)

I fixed the issue with the symlink method: sudo ln -s /usr/lib/libjsoncpp.so.21 /usr/lib/libjsoncpp.so.20

https://github.com/polybar/polybar/wiki/Known-Issues#error-while-loading-shared-libraries-libjsoncpp

https://www.shellhacks.com/symlink-create-symbolic-link-linux/

No other package has broken so far.

patrick96 commented on 2019-09-19 13:13 (UTC)

@zack6849 neither, recompiling polybar will fix it. See https://github.com/polybar/polybar/wiki/Known-Issues#error-while-loading-shared-libraries-libjsoncpp

« First ‹ Previous 1 2 3 4 5 Next › Last »