Package Details: vicious-git 2.3.3.r0.gea0c5a4-1

Git Clone URL: (read-only, click to copy)
Package Base: vicious-git
Description: Widgets for the Awesome window manager
Upstream URL:
Licenses: GPL2
Conflicts: vicious
Provides: vicious
Submitter: None
Maintainer: alerque
Last Packager: alerque
Votes: 132
Popularity: 0.000000
First Submitted: 2009-08-27 19:45 (UTC)
Last Updated: 2019-08-26 05:34 (UTC)

Dependencies (6)

Required by (3)

Sources (1)

Latest Comments

alerque commented on 2019-03-12 13:09 (UTC)

@nasedo and @khughitt This package has been updated based on that fork (which seems to be the official one now that the old URL is forwarding there).

khughitt commented on 2017-03-02 14:44 (UTC)

I second the suggestion to switch to Mic92's repo - the original repo does not appear to be maintained anymore while fixes are being accepted at the Mic92 repo.

nasedo commented on 2016-12-28 17:22 (UTC)

Repository at seems to be more up to date than the one this package is using. Why not switch to it?

angvp commented on 2015-05-19 03:34 (UTC)

Lua 5.3 got in extra, advice from @terminalmage is a proper solution.

terminalmage commented on 2015-05-18 15:39 (UTC)

This PKGBUILD needs to be updated since Lua 5.3 hit [extra]. In particular, rather than hardcoding _luaver, you might consider doing something like this at the top of the package() function: _luaver=`lua -v | cut -f2 -d' ' | cut -f1,2 -d.` Doing this would keep the PKGBUILD from needing an update every time Lua gets a minor/major version bump.

anrxc commented on 2014-10-15 13:13 (UTC)

> depends=("lua") > makedepends=("git") Hi. Did the "makedepends" keyword change?

Dasonk commented on 2014-10-06 00:03 (UTC)

You should add git as a make dependency

anrxc commented on 2013-11-23 20:10 (UTC)

Nice new feature with shared timers in v2.1.1.9.g211d450-1. But I could use some help testing it, anyone hits a bug in it let me know. Thanks!

anrxc commented on 2013-11-14 16:37 (UTC)

Thanks bidulock - previously package in extra installed in a different path so there was no real conflict. The describe seems the same, can you revise it and send it again please? Thanks.

bidulock commented on 2013-11-14 07:40 (UTC)

Thanks for the package. Needs provides=("vicious") conflicts=("vicious") in PKGBUILD. Also, git describe --always | sed 's|^[^0-9]*||;s|\.g[a-f0-9]*$||;s|-|.|g' yeilds a better pkgrel.

anrxc commented on 2013-04-14 15:41 (UTC)

Thanks, I'll look into that.

KaiSforza commented on 2013-04-10 21:45 (UTC)

This should be updated to reflect the new pacman 4.1 source array and version scheme.

commented on 2012-12-29 22:55 (UTC)

Ah, thanks.

anrxc commented on 2012-12-29 22:35 (UTC)

This will become a symlink /usr/share/lua/5.1/vicious after the upgrade. You can delete it before the upgrade.

commented on 2012-12-29 19:05 (UTC)

What kind of manual intervention is required on upgrade? Should I use --force? (1/1) checking package integrity (1/1) loading package files (1/1) checking for file conflicts error: failed to commit transaction (conflicting files) vicious-git: /usr/share/lua/5.1/vicious exists in filesystem Errors occurred, no packages were upgraded. ==> WARNING: Failed to install built package(s).

anrxc commented on 2012-12-15 21:36 (UTC)

Vicious is now usable with awesome and awesome-git. With lua51 and lua52. 20121215-3: Manual intervention required on upgrade.

cocreature commented on 2012-12-15 17:08 (UTC)

imho vicious stable (community) is for awesome stable and vicious-git should be for awesome-git.

anrxc commented on 2012-12-15 17:05 (UTC)

Package 'awesome' in community is not lua 5.2 compatible so it may not have 5.2 in the module search path. I will have to test that, and just maybe keep using 5.1 until 3.5 is released.

krionux commented on 2012-12-15 10:20 (UTC)

Hello, As Javafant said, please update luaver in order to build against lua5.2 Regards,

cocreature commented on 2012-12-13 15:31 (UTC)

_luaver needs to be changed to 5.2.

anrxc commented on 2012-07-09 23:19 (UTC)

Commit b11bb78e04 was a little different because the protocol was telnet (or so I thought). In any case without a network connection, because of "--connect-timeout 1 -fsm 3", curl wasn't ever supposed to hang more than 1 second. I'll look into that.

anrxc commented on 2012-06-25 14:41 (UTC)

Hello we don't have a clock widget type: > vicious = require("vicious") Yes that's the way you load now, with lua5.1 and lua5.2.

gbr commented on 2012-06-25 07:55 (UTC)

@anrxc Okay I had to change the line below in my rc.lua because after the update, awesome wm wasn't loading anymore: >require("vicious") to: >vicious = require("vicious") then to load/register a widget: >vicious.register(clock, blah, blah... Is this the "correct way"? Thank you.

anrxc commented on 2012-06-25 00:05 (UTC)

Vicious is now treated as a regular Lua library, as it can be used stand-alone or to feed widgets of other window managers: $ lua > widgets = require("vicious.widgets") > print(widgets.volume(nil, "Master")[1]) 100

anrxc commented on 2012-06-20 23:09 (UTC)

Vicious ported to Lua 5.2. It changes the way module is loaded to remain compatible with Lua 5.1 installations. One line change, see top of the README.

commented on 2011-12-20 17:32 (UTC)

anrxc: check

anrxc commented on 2011-12-20 15:43 (UTC)

bunburya for some reason you are connecting to port 8080. Web server is on port 80. uzsolt if that is the proper way to handle it then it's fine with me.

commented on 2011-12-20 08:07 (UTC)

@bunburya: works for me, git 1.7.8. @anrxc: what do you think change to 'noarch'?

commented on 2011-12-20 02:47 (UTC)

Installation fails on my system, with the following message: ==> Connecting to GIT server over HTTP... Cloning into 'vicious'... error: Failed connect to; Connection timed out while accessing fatal: HTTP request failed ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build vicious-git. I am able to access in Firefox. For some reason, "git clone" doesn't work on git v1.7.8 on ArchLinux (just says "Cloning into 'vicious'" and hangs), whereas it works perfectly on git v1.7.2.5 on Debian. This seems to be similar to the problem experienced by thelastknowngod, but it seems that the problem was solved for him/her.

anrxc commented on 2011-12-03 18:34 (UTC)

Removed obsolete OR handlers and updated .install file. There's no reason to upgrade your package.

commented on 2011-11-29 06:11 (UTC)

Should not update pkgver? I think 20100930 is too old ;)

anrxc commented on 2010-10-08 20:28 (UTC)

Notice for awesome-git users: initiall support for the new widget system was added. Upgrade freely.

commented on 2010-09-07 12:27 (UTC)

If anyone out there is using the latest (as of Sep 07, 2010) awesome-git and vicious-git together, having vicious.register anywhere in your rc.lua will break things. To fix this, edit /usr/share/awesome/lib/vicious/init.lua, and on line 120, change 'add_signal' to 'connect_signal.'

anrxc commented on 2010-04-22 13:47 (UTC)

I acknowledge there is/was a problem, but it's not as bad as 'completely broken'. I hope smart http solves everything.

commented on 2010-04-21 19:59 (UTC)

worked today when i tried the install. it was not working for the last two days. i wasnt the only one who had a problem either. i dont know what you did and i dont really care. just thought id let you know. no need to be so dismissive.

commented on 2010-04-21 03:08 (UTC)

adding a slash allows me to view the web info but the git clone that is specified in the pkgbuild does not work. i let it work at 2 different locations for an hour each and it never went further than the "Initializing empty Git repository" stage. the pkgbuild does not work.

anrxc commented on 2010-04-20 23:52 (UTC)

That is the clone URL. If you want to visit the web interface append a slash to the end. Edit: Latest git versions now include the "smart HTTP" protocol which we will implement, so we should get past these stupid limitations.

commented on 2010-04-20 19:49 (UTC)

the repository is empty. going to with firefox says "No repositories found"

anrxc commented on 2010-04-19 17:17 (UTC)

Repository is served over HTTP, which is a "stupid" git protocol, seeing no output while it's getting the objects doesn't necessarily mean something went wrong. I just built the package, in addition.

commented on 2010-04-19 16:05 (UTC)

stalls connecting to GIT server. Initialized empty Git repository in /tmp/yaourt-tmp-root/aur-vicious-git/vicious-git/src/vicious/.git/