Arch Linux User Repository

Installs with official instructions to /opt. Read here for more information and options for the systemd service. ( -> e) manual) The search engine is accessible at localhost:5000, set it as default engine using your browsers option. Binary builds are available at Chaotic-AUR!

That issue is fixed :)

I still cant' get it to work, v0.6.0.5:

$ yay -Si  whoogle

:: Querying AUR...
Repository      : aur
Name            : whoogle
Keywords        : engine  search  whoogle
Version         : 0.6.0-5
First Submitted : Thu 08 Apr 2021 10:52:41 AM WEST
Last Modified   : Thu 21 Oct 2021 12:17:07 PM WEST
Out-of-date     : No

$ sudo systemctl start  whoogle.service

Oct 26 01:00:49 gigabyty systemd[1]: whoogle.service: Main process exited, code=exited, status=1/FAILURE
Oct 26 01:00:49 gigabyty systemd[1]: whoogle.service: Failed with result exit-code.
Oct 26 01:00:53 gigabyty systemd[1]: whoogle.service: Main process exited, code=exited, status=1/FAILURE
Oct 26 01:00:53 gigabyty systemd[1]: whoogle.service: Failed with result exit-code.

whoogle-git also doesnt even install:

[Aur:1] whoogle-git-0.6.0_r391.g20976f2-1

:: (1/1) Parsing SRCINFO: whoogle-git                                               
==> Making package: whoogle-git 0.6.0_r391.g20976f2-1 (Tue 26 Oct 2021 01:06:12 AM W
EST)                                                                                
==> Retrieving sources...                                                           
  -> Cloning whoogle-search git repo...                                             
....

seems to go ok, but then:

soupsieve-1.9.5 stem-1.8.0 toml-0.10.2 urllib3-1.26.5 waitress-1.4.3 wcwidth-0.1.9
WARNING: You are using pip version 21.2.3; however, version 21.3.1 is available.
You should consider upgrading via the /dev/shm/aurydesty/whoogle-git/src/whoogle-search/venv/bin/python3 -m pip install --upgrade pip command.
rm: cannot remove .github: No such file or directory
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: whoogle-git

Thanks for the feedback @Locutus64. Sorry for the issues, I just pushed an update which should fix them. If there are still issues, please report them :)

A update to 6.0.4 was pushed that fixes my issue.

I just got the latest testing update for Manjaro and after a reboot and launching Vivaldi I noticed Whoogle didn't launch. I closed Vivaldi and checked Whoogles status and got the below. I have also tried to enable and start whoogle's service and still the below. Running the latest Manjaro with KDE Plasma 2.23 desktop

    ~  sudo systemctl status whoogle                                                                    ✔ 
[sudo] password for locutus: 
Sorry, try again.
[sudo] password for locutus: 
● whoogle.service - Whoogle
     Loaded: loaded (/usr/lib/systemd/system/whoogle.service; enabled; vendor preset: disabled)
     Active: activating (auto-restart) (Result: exit-code) since Wed 2021-10-20 04:55:03 PDT; 2s ago
    Process: 19351 ExecStart=/opt/whoogle-search/venv/bin/python3 -um app --host 0.0.0.0 --port 5000 (code=exit>
   Main PID: 19351 (code=exited, status=1/FAILURE)
        CPU: 191ms
lines 1-6/6 (END)

    ~  journalctl -u whoogle                                                                            ✔ 
-- Journal begins at Tue 2021-08-31 09:47:11 PDT, ends at Wed 2021-10-20 09:35:36 PDT. --
Aug 31 11:45:50 Borg-Cube systemd[1]: Started Whoogle.
Aug 31 11:45:59 Borg-Cube whoogle[30895]: Serving on http://0.0.0.0:5000
Aug 31 11:52:21 Borg-Cube systemd[1]: Stopping Whoogle...
Aug 31 11:52:21 Borg-Cube systemd[1]: whoogle.service: Deactivated successfully.
Aug 31 11:52:21 Borg-Cube systemd[1]: Stopped Whoogle.
Aug 31 11:52:21 Borg-Cube systemd[1]: whoogle.service: Consumed 4.131s CPU time.
-- Boot 3790d15859ff46a4b39bdaf2e2bd164b --
Aug 31 11:53:07 Borg-Cube systemd[1]: Started Whoogle.
Aug 31 11:53:12 Borg-Cube whoogle[1367]: Serving on http://0.0.0.0:5000
Aug 31 17:15:51 Borg-Cube systemd[1]: Stopping Whoogle...
Aug 31 17:15:51 Borg-Cube systemd[1]: whoogle.service: Deactivated successfully.
Aug 31 17:15:51 Borg-Cube systemd[1]: Stopped Whoogle.
Aug 31 17:15:51 Borg-Cube systemd[1]: whoogle.service: Consumed 1.236s CPU time.
-- Boot 87514747bd054a91aff2efd2028dab99 --
Aug 31 17:16:39 Borg-Cube systemd[1]: Started Whoogle.
Aug 31 17:16:44 Borg-Cube whoogle[1675]: Serving on http://0.0.0.0:5000
Aug 31 17:35:50 Borg-Cube systemd[1]: Stopping Whoogle...
Aug 31 17:35:50 Borg-Cube systemd[1]: whoogle.service: Deactivated successfully.
Aug 31 17:35:50 Borg-Cube systemd[1]: Stopped Whoogle.
-- Boot 49f2c970f67d49678427e86e1a5e786e --
Aug 31 17:36:37 Borg-Cube systemd[1]: Started Whoogle.
Aug 31 17:36:42 Borg-Cube whoogle[1694]: Serving on http://0.0.0.0:5000
Aug 31 17:39:39 Borg-Cube systemd[1]: Stopping Whoogle...
Aug 31 17:39:39 Borg-Cube systemd[1]: whoogle.service: Deactivated successfully.

Here goes one more vote for this tool.

Just found out about whoogle and discovered someone had already something setup on AUR. Wow, long live the AUR and Arch.

This is a very interesting, usefull, and intriguing tool.

But it really needs to have a lot of eyes watching it to make sure it gets installed the "right way" in Arch. The upstream developers seem to take care of providing and updating constantly lotz of instructions. This, and https://aur.archlinux.org/packages/whoogle-git/ should be ideally maintained by the same persons.

Might also be really usefull in a separate Arch pc in the local network, or a rented server.

Just a big thanks to all the involved and their effort and attention to detail, dr460nf1r3, kseistrup, astier.

Here's a couple of observations, currently testing v0.6, not necessarly bug reports:

1. Currently failing with v0.6

2. This PKGBUILD decides to have the Systemd unit enabled and started by default

3. Leftovers after uninstall

1. Currently failing with v0.6

Installation seems to be going ok, but then:

Running 'pacman -U aurydesty/whoogle/whoogle-0.6.0-3-x86_64.pkg.tar.zst'
transaction started                                                                 
installed whoogle (0.6.0-3)   
Created symlink /etc/systemd/system/multi-user.target.wants/whoogle.service → /usr/lib/systemd/systemd/whoogle.service.


chown: cannot access '/opt/whoogle-search/app/static/config': No such file or directory

sudo systemctl restart whoogle:

whoogle.service: Main process exited, code=exited, status=1/FAILURE
whoogle.service: Failed with result 'exit-code'.

2. This PKGBUILD decides to have the Systemd unit enabled and started by default

Enabled the Whoogle systemd service.                                                
Visit localhost:5000 to start searching!

I'm not sure this is the standard and correct way of doing this. Perhaps this should be left to the user to decide ? So that he can:

• first inspect what was installed, eventually decide to customize /etc/defaults etc
• then do a test run with sudo systemctl start whoogle
• then if he decides, do sudo systemctl enable whoogle

3. Leftovers after uninstall

Running, yay -S whoogle to install, and then pacman -Rns whoogle to uninstall it again

Leaves behind as a leftover:

/etc/systemd/system/multi-user.target.wants/whoogle.service

pacman -Qo /etc/systemd/system/multi-user.target.wants/whoogle.service:

error: No package owns /etc/systemd/system/multi-user.target.wants/whoogle.service

file /etc/systemd/system/multi-user.target.wants/whoogle.service

/etc/systemd/system/multi-user.target.wants/whoogle.service: broken symbolic link to /usr/lib/systemd/system/whoogle.service

Also added. Thanks a lot!

You should probably have a

chown -R whoogle.whoogle /opt/whoogle-search/app/static/config

in your post_{install,upgrade} hooks, otherwise whoogle won't be able to save its configuration.

Also, you should use 127.0.0.1 as the listening address (and it really ought to be configurable) instead of listening to “everything”. You can make it configurable be installing a /etc/default/whoogle file with these contents:

BIND_ADDRESS=127.0.0.1
LISTEN_PORT=5000

and then change whoogle.service to reflect this:

EnvironmentFile=-/etc/default/whoogle
ExecStart=/opt/whoogle-search/venv/bin/python -um app --host $BIND_ADDRESS --port $LISTEN_PORT

Also, you should neither enable, nor start the service, as the user may want to configure their frontend or their firewall first.

You can make a user aware of the default values (and the file to configure it) during install.

Also, since the app is MIT licensed, you should copy LICENSE to the licenses directory, e.g.:

install -Dm0644 LICENSE "$pkgdir/usr/share/licenses/$pkgname/LICENSE"

Ugh, I misunderstood you. I hope everything is fine now! :)

You missed the -D in the install -Dm0644 commands.