Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - i3blocks-git

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: i3blocks-git 1.4.r21.g017395f-2

Git Clone URL: https://aur-dev.archlinux.org/i3blocks-git.git (read-only)
Package Base: i3blocks-git
Description: Define blocks for your i3bar status line
Upstream URL: https://github.com/vivien/i3blocks
Licenses: GPL3
Conflicts: i3blocks
Provides: i3blocks
Submitter: Runiq
Maintainer: Foxboron
Last Packager: Foxboron
Votes: 11
Popularity: 0.171406
First Submitted: 2014-06-02 19:10
Last Updated: 2016-07-31 13:21

Dependencies (9)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

Foxboron commented on 2016-07-31 13:19

Thank you for the heads up! Updating the package

alexlu commented on 2016-07-31 12:39

colors.patch is not needed since it got merged.

Foxboron commented on 2016-05-30 14:50

Added bc and lm_sensors from the i3blocks package!

bacon commented on 2016-05-30 14:44

I feel like `bc` should be listed in optdepends (for the default bandwidth script). It's there in the main i3blocks package, but not this one.

Without it the script will still run, but values above the KB range will only display "M" instead of "3.2M".

stef204 commented on 2016-05-15 16:09

As I mentioned before, I think you had it just right, before the last revert.
The dir path change is really only due to the previous packager whom had used /usr/libexec/i3blocks/ "erroneously".
And the warnings included in our comments here are probably enough.
I think undoing the last revert + color patch are the key issues.

Foxboron commented on 2016-05-15 15:45

I'll take a look at the patch and tripple check the PKGBUILD before doing something more.
Ill also add a notice about the dir change!

stef204 commented on 2016-05-15 13:52


No worries, it's on me.
According to https://wiki.archlinux.org/index.php/Arch_packaging_standards#Package_etiquette you did the right thing by switching to /usr/lib/i3blocks/ as opposed to /usr/libexec/i3blocks/.
So go back to what you had before you reverted just now.
I think the unexpected effect that it would remove the scripts in /usr/libexec/i3blocks/ is more due to pacman/makepkg as there is nothing in your script that removes the scripts in /usr/libexec/i3blocks/.
I've adjusted my i3blocks.conf to point to /usr/lib/i3blocks/ and did whatever edits I could remember as a quick fix.
Again, my bad as I didn't back up my scripts (some which are in ~/bin were not affected, obviously.)
I think a warning that the scripts directory would change might have helped but really it's on me.
Anyway, just try to address the color issue/patch, if you are so inclined. Thanks.

Foxboron commented on 2016-05-15 13:35

Reverted it all and looking into it. So sorry for the trouble!

stef204 commented on 2016-05-15 07:03

Result of this upgrade is that ALL of the scripts that were contained in /usr/libexec/i3blocks (some of which were painstakingly edited) are gone.
So this update broke i3blocks.
I doubt this is what the author intended (to remove/delete all pre-existing scripts contained in the dir quote above.)
My bad for not backing up my scripts and not reading the PKGBUILD in detail before upgrading (I did do a diff and it "seemed" OK.)
Line 34 can't quite be right:
IMHO LIBEXECDIR=/usr/lib install is incorrect. Why do this when previous version had the dir as such: /usr/libexec/i3blocks ?
OR are you saying previous version PKGBUILD was incorrectly written and scripts dir should always have been /usr/lib/i3blocks/ ?
Colors are broken, i.e. no colors.
Colors do work for stable release i3blocks in AUR.
You might consider applying the patch given in issue 146 to your PKGBUILD.

Foxboron commented on 2016-05-14 13:43

Sorry for the slow response.
Should be fixed now!