Package Details: pix 2.8.9-1

Git Clone URL: (read-only, click to copy)
Package Base: pix
Description: Image viewer and browser based on gthumb. X-Apps Project.
Upstream URL:
Licenses: GPL
Conflicts: pix-git
Provides: pix
Submitter: ion203
Maintainer: ion203
Last Packager: ion203
Votes: 31
Popularity: 0.74
First Submitted: 2016-08-26 04:45 (UTC)
Last Updated: 2022-12-16 16:25 (UTC)

Latest Comments

1 2 Next › Last »

ion203 commented on 2022-12-12 15:34 (UTC)

Automake is not listed in makedepends because having the base-devel group installed is a prerequisite to building AUR packages.

desbma commented on 2022-12-12 13:16 (UTC)

This needs automake in makedepends.

twa022 commented on 2022-05-23 13:46 (UTC)

By default pix uses dcraw to load RAW images unless you pass --enable-libopenraw to configure (disabled by default), so you can remove libopenraw from makedepends

spsf64 commented on 2020-11-28 01:40 (UTC)

@ion203: thanks for the feedback and for maintaining this package!

ion203 commented on 2020-11-28 01:35 (UTC)

Though this issue is resolved now, here are the relevant bugs filed for anyone curious coming across this with maui/pix in mind:

spsf64 commented on 2020-11-28 00:09 (UTC) (edited on 2020-11-28 00:10 (UTC) by spsf64)

@ion203, they renamed the package! No more conflicts!

ion203 commented on 2020-11-26 22:52 (UTC)

Well that's annoying -_-

Mirrored this package to pix-xapp for now:

spsf64 commented on 2020-11-25 23:36 (UTC)

@ion203: there is a new package in the std arch repos with the same name, this will cause conflict with this package, maybe rename it? See:

3y7cd commented on 2019-12-10 06:27 (UTC) (edited on 2019-12-10 06:27 (UTC) by 3y7cd)

pix is no longer depend on gonf, and here is for details:
Please remove that from dependencies list.


ion203 commented on 2019-01-16 01:39 (UTC)

The file that's causing the error, "", isn't in the package; it's generated by autoconf which is required by gnome-common. Just spitballing, maybe there's an issue with your autoconf installation which may be resolved by performing a system upgrade / reinstallation of gnome-common and related packages. If not the latest, it may be useful to see what version of gnome-common/autoconf is being used and whether the same issue can be reproduced in a clean chroot [1] on your own system.