Package Details: mugshot 0.4.2-1

Git Clone URL: https://aur.archlinux.org/mugshot.git (read-only, click to copy)
Package Base: mugshot
Description: Program to update personal user details
Upstream URL: https://github.com/bluesabre/mugshot
Licenses: GPLv3
Submitter: None
Maintainer: twa022
Last Packager: twa022
Votes: 80
Popularity: 2.35
First Submitted: 2014-10-06 21:37
Last Updated: 2019-08-31 00:54

Latest Comments

1 2 3 4 Next › Last »

DaComicalSans commented on 2020-05-18 04:48

Depreciated?

D3SOX commented on 2019-08-30 13:48

New URL is https://github.com/bluesabre/mugshot

michaelnix commented on 2019-07-16 17:38

Never mind. I guess it was a problem with pamac-aur. Yay built just fine.

michaelnix commented on 2019-07-16 11:21

Fails to clone files for building. Comes back null.

FredBezies commented on 2018-08-08 15:30

Mugshot 0.4.1 is out.

https://bluesabre.org/2018/08/08/mugshot-0-4-1-released/

KillWolfVlad commented on 2018-08-06 12:22

Must be rebuilt for work with python 3.7.0-3

friday13 commented on 2018-07-24 12:58

UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 92: ordinal not in range(128) ==> ERROR: A failure occurred in package(). Aborting... 2018-07-24 15:57:13,580 - wrappers - makepkg - ERROR - makepkg query ['makepkg', '-cf', '--noconfirm'] failed in directory /home/friday13/.cache/aurman/mugshot

thaewrapt commented on 2018-03-23 13:04

Seems like this package intended to work with Python2, not Python3. So, fixing all dependencies to python2-* ones is more convenient way to deal with locale error (and any others possible).

burningbronx commented on 2018-01-17 19:45

Another way to fix the "UnicodeDecodeError" is to set encoding='UTF-8' where the open() method is invoked in Setup.py. Build compiles.

jonathon commented on 2017-12-11 16:52

Looks like "UnicodeDecodeError" is due to a default C locale instead of a UTF8 locale. One workaround is to edit /etc/locale.gen and enable en_US.UTF8, then run locale-gen, then export LC_ALL=en_US.UTF8. Build will complete after that.

Not sure if that's in the scope of a PKGBUILD? It kind of sounds like a bug in the upstream code...