I'm using this package with my awesome wm on my laptop a long time. all work very well. x86 ok. Please stabilize. Reproducible: Always
um, why not 2.0.3?
(In reply to comment #1) > um, why not 2.0.3? Indeed. I tried build and run v. 2.0.3. all ok on my x86 laptop
*bump*
repoman: file.UTF8 4 /usr/portage/x11-plugins/vicious/vicious-2.0.2.ebuild: line 1, just after: '' /usr/portage/x11-plugins/vicious/vicious-2.0.1.ebuild: line 1, just after: '' /usr/portage/x11-plugins/vicious/vicious-2.0.3.ebuild: line 1, just after: '' /usr/portage/x11-plugins/vicious/ChangeLog: line 1, just after: '' ebuild.allmasked 1 x11-plugins/vicious
I don't see any reason why not. I'm not getting those errors with repoman. Arches, please test and stabilize =x11-plugins/vicious-2.0.3 thanks
amd64: Pass I've been using it for a while, works fine.
amd64: ok (I tried importing it and one widget on current stable awesome and lua).
+ 17 Mar 2012; Tony Vroon <chainsaw@gentoo.org> vicious-2.0.3.ebuild: + Marked stable on AMD64 based on arch testing by Elijah "Armageddon" El + Lazkani & Tomáš "Mepho" Pružina in bug #399691.
ping for x86 devs
x86 stable
Please mark stable for arm, last arch
arm passes, we'll wait for a user request. closing.