Package Details: archey3-git 0.4.r57.gac68752-1

Git Clone URL: https://aur.archlinux.org/archey3-git.git (read-only, click to copy)
Package Base: archey3-git
Description: Python script to display system information alongside the Arch Linux logo.
Upstream URL: https://lclarkmichalek.github.io/archey3/
Keywords: info system
Licenses: GPL
Conflicts: archey, archey3, archey4
Provides: archey
Submitter: xyproto
Maintainer: HLFH
Last Packager: HLFH
Votes: 172
Popularity: 0.44
First Submitted: 2013-11-02 12:03 (UTC)
Last Updated: 2022-12-30 18:10 (UTC)

Dependencies (6)

Required by (0)

Sources (1)

Latest Comments

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

graysky commented on 2013-06-22 14:43 (UTC)

@BlueP - Will you update the PKGBUILD for pacman 4.x? https://github.com/bluepeppers/archey3/pull/14

BluePeppers commented on 2013-05-16 20:34 (UTC)

I see them, I just don't respond most of the time (or leave it a few months before responding). Oh the joys of being lazy. As graysky said, submit a pull request, otherwise I'll implement the change at some point in the future :) I agree that sanitization of the CPU model is something that is a tad lacking at the moment.

graysky commented on 2013-05-16 20:29 (UTC)

techb - If you feel it's value-added send a pull request on github. The dev is likely not to see your comment here.

<deleted-account> commented on 2013-05-16 20:18 (UTC)

I modified the archey script in /usr/bin/archey line 390 in the class cpuDisplay. Before I modified it, the cpu model name had a lot of white space between the words and would make a newline and mess up the logo. Old: infodict[k.strip()] = v.strip() Changed: infodict[k.strip()] = ' '.join(v.split()) Works much better.

BluePeppers commented on 2013-02-28 12:44 (UTC)

So the problem is that XDG_CONFIG_HOME is no longer defined. This isn't actually uncommon, and archey3 uses ~/.archey3.cfg when that happens. As far as I'm concerned, that's expected behavior. However, as people are now resetting their XDG_CONFIG_HOME's, I think some might be doing `export XDG_CONFIG_HOME='$HOME/.config'`. This is not good, as it means that XDG_CONFIG_HOME is set to "$HOME/.config", _not_ "<the value of $HOME>/.config". I've committed a fix for this (it's ugly and breaks if you have a $ in your username (which is unlikely)). That said, archey3 still isn't great at handling bad config file loading and stuff. That FileNotFoundError never should have happened, and while I think I've solved that, I can still see a few ways to break it (all of which I am too lazy to fix right now). Anyway, hopefully the latest couple of commits should have fixed some of the problems, though I can believe it'll just SyntaxError as soon as you run it ;)

Antunes commented on 2013-02-28 11:44 (UTC)

I found the relevant bug discussion here: https://bugs.archlinux.org/task/31204 It might be a good idea to use an absolute path instead of those variables, as ivantomica pointed out before.

graysky commented on 2013-02-26 21:15 (UTC)

I am getting this too... something changed with our systems, not with archey3. Where is $XDG_CONFIG_HOME defined on Arch by default and why has it suddenly disappeared?

<deleted-account> commented on 2013-02-26 19:38 (UTC)

You could also do something like: export XDG_CONFIG_HOME="$HOME/.config" i did that on my main machine and it started reading good config file.. :)

Antunes commented on 2013-02-26 13:31 (UTC)

Hmm, my $XDG_CONFIG_HOME is currently set to /home/$user, not to /home/$user/.config. That's why it cannot find the file.

<deleted-account> commented on 2013-02-26 13:02 (UTC)

Antunes: i just changed $XDG... in /usr/bin/archey to absolute path (e.g. /home/$user/.config/archey3.cfg

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