Package Details: inox-bin 67.0.3396.87-1

Git Clone URL: (read-only)
Package Base: inox-bin
Description: Chromium Spin-off to enhance privacy by disabling data transmission to Google. (binary version)
Upstream URL:
Keywords: browser chromium web
Licenses: BSD
Conflicts: inox
Provides: inox
Submitter: gcarq
Maintainer: gcarq
Last Packager: gcarq
Votes: 75
Popularity: 0.964295
First Submitted: 2015-06-22 19:49
Last Updated: 2018-06-21 18:01

Dependencies (35)

Required by (0)

Sources (1)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

victor3d commented on 2018-09-04 15:14

Please recompile to get rid of error without any workarounds

NullRoute commented on 2018-08-16 11:37

See workaround here;

Cravix commented on 2018-08-09 03:05

icu update breaks the dependency of this packages, now I get the error

/usr/lib/inox/inox: error while loading shared libraries: cannot open shared object file: No such file or directory

every time running inox.

Please recompile, and thanks in advance :)

Shadowdodger2 commented on 2018-06-23 10:08

Is the latest version (67.0.3) working without any issues?

gcarq commented on 2018-06-21 18:02

Thanks for the gists. Updated the PKGBUILD accordingly

cookiengineer commented on 2018-06-18 20:19

Can you please update the PKGINFO and add the removal of the dotfiles to the package() method? Afterwards, the package works perfectly fine. Before it, makepkg -s will fail because dotfiles were in the root folder of the extracted archive.

Uploaded the diff to this gist here:

air-g4p commented on 2018-06-03 01:35

Thank you glitsj16. Your updated PKGBUILD works perfectly. Indeed, I read about the issues the transition to pacman 5.1 is causing daily on #archlinux. I appreciate your effort.

glitsj16 commented on 2018-06-01 02:12

The reported tar warnings are a BSD tar vs. GNU tar issue and harmless in this context. The fatal errors are indeed related to pacman 5.1, which has a check script running during the package() phase. Here's a pacman 5.1 compatible PKGBUILD (with additional suppression of the reported tar warnings).

halocaridina commented on 2018-05-31 20:36

Seeing the same sort of fatal errors as @air-g4p on two machines. My gut feeling was some change in makepkg with the recent release of pacman 5.1 so downgraded to pacman 5.0.2-3 and inox-bin was built successfully (i.e., no dotfile found errors). So appears that PKGBUILD of inox-bin needs tweaks to be compatible with makepkg from pacman 5.1 and that @hotdog789 has pacman<5.1.

hotdog789 commented on 2018-05-31 02:01

easy install, no issues.