Package Details: cerebro 0.3.2-1

Git Clone URL: (read-only, click to copy)
Package Base: cerebro
Description: Open-source productivity booster with a brain.
Upstream URL:
Keywords: cerebro electron launcher search
Licenses: MIT
Conflicts: cerebro-git
Provides: cerebro
Submitter: maximbaz
Maintainer: victori
Last Packager: maximbaz
Votes: 16
Popularity: 0.000000
First Submitted: 2017-02-01 15:10 (UTC)
Last Updated: 2018-01-26 19:51 (UTC)

Latest Comments

markboston35 commented on 2020-05-21 18:08 (UTC)

so is this dead?

tnilzon commented on 2020-01-24 07:38 (UTC)

When trying to install on Manjaro I get this error:

could not satisfy dependencies: unable to satisfy dependency 'nodejs-lts-carbon' required by cerebro

keiichiiownsu12 commented on 2019-09-30 00:29 (UTC)

when attempting to run, error is returned, saying Pango-ERROR **: Harfbuzz version too old (1.3.1)

will this app be pointless to run from now on? I know this app has not been maintained by the original coder for 2 years now

maximbaz commented on 2018-03-31 17:33 (UTC)

Cerebro has not been maintained for a few months now, and I have switched to a different application launcher - rofi. I like it very much and I think I'm staying permanently with it.

I'm thus disowning this AUR package, please feel free to take over maintaining it, in case new versions will ever be released.

maximbaz commented on 2018-01-26 19:56 (UTC) (edited on 2018-03-31 16:33 (UTC) by maximbaz)

Although the bug is still valid and it is impossible to compile cerebro using nodejs v9, I decided to add nodejs v8 to makedepends, so that those of you who build AUR packages in chroot (e.g. via aurutils) will be able to upgrade.

whenov commented on 2018-01-16 11:37 (UTC)

@maximbaz Thanks for the explanation!

maximbaz commented on 2018-01-15 11:39 (UTC)

This is certainly possible, but I'd suggest creating a new AUR package cerebro-bin. The convention is to name AUR packages cerebro if we build the app from sources, and cerebro-bin if we use pre-compiled binaries (such as deb package).

However, talking specifically about cerebro, I must say I've seen more than one case when pre-compiled packages were not based on the release tarball. I'm not exactly sure how that happened, I believe this was a honest mistake, but again - it happened more than once.

That's why I'm personally sticking to this package, at least I can be sure exactly on what source code it is built.

If you create cerebro-bin, feel free to add me as co-maintainer and I'll be updating the pkgversion as new releases are created, I already have a watcher configured monitoring github releases page.

whenov commented on 2018-01-15 11:13 (UTC)

@maximbaz Why do we build it since there's a deb package?

maximbaz commented on 2017-12-18 13:28 (UTC)

0.3.2 was released recently and has some nice improvements, but it doesn't compile on Arch Linux. Make some noise on the tracking ticket to bring the developer's attention to it, or maybe even suggest a fix :P

maximbaz commented on 2017-11-20 11:25 (UTC)

It is not out-of-date, 0.3.1 is the last available version.

maximbaz commented on 2017-09-03 12:18 (UTC)

The build issue is fixed with the 0.3.1 version.

maximbaz commented on 2017-07-02 20:24 (UTC)

The build is failing now, tracking issue:

Deuchnord commented on 2017-06-26 09:34 (UTC)

Oh, sorry, I got confused :s I'll take more attention to this, I promise!

maximbaz commented on 2017-06-23 16:17 (UTC)

@Deuchnord this package is not out-of-date, and it is not an elasticsearch web admin tool [1], it is an application launcher [2] :) [1]: [2]:

maximbaz commented on 2017-03-28 08:08 (UTC)

Hi @hcorion, that is an interesting finding. Do you think `cd "${srcdir}"` or `cd "${srcdir}/${pkgname}-${pkgver}"` should be added? Could you please try to locally edit the PKGBUILD and see if adding any of these lines help?

hcorion commented on 2017-03-28 01:34 (UTC)

Hmm, Interesting if I manually run gendesk -f -n --name=Cerebro --pkgname="cerebro" --pkgdesc="asdfasdf" --exec="cerebro" --categories="System" Then it works fine. Perhaps if you add cd "${srcdir}" Before the call to gendesk?

hcorion commented on 2017-03-28 01:30 (UTC)

@maximbaz I'm having the same problem as brk0_0, I'm also using pacaur, perhaps that has something to do with it? It makes sense, I don't see any cerebro.desktop file anywhere. How is the file generated, what package is generating it?

maximbaz commented on 2017-03-13 16:21 (UTC)

Hey @jobu, I can add ICU if you say it's required, but let's first ensure it helps you building the package. Interestingly enough, I have ICU installed (it is a dependency of so many other apps), and on my system I also have v58 (except libreoffice and dropbox packaging their own versions): ❯ la /**/* -rw-r--r-- 1 root root 1.8M Mar 13 02:17 /opt/dropbox/ lrwxrwxrwx 1 root root 18 Dec 10 09:26 /usr/lib/ -> lrwxrwxrwx 1 root root 18 Dec 10 09:26 /usr/lib/ -> -rwxr-xr-x 1 root root 2.5M Dec 10 09:26 /usr/lib/ -rwxr-xr-x 1 root root 2.5M Mar 9 15:00 /usr/lib/libreoffice/program/ And I've just tried to reinstall this package, the build is successful.

jobu commented on 2017-03-13 16:13 (UTC)

I think ICU is also a dependency and I cannot build with latest ICU version: Avvio di build() in corso... node: error while loading shared libraries: cannot open shared object file: No such file or directory node: error while loading shared libraries: cannot open shared object file: No such file or directory In fact on my system I have not 57

maximbaz commented on 2017-03-08 15:15 (UTC)

@brk0_0 I've just tried to build it from scratch, unfortunately I can't reproduce your issue. Does anyone else have this problem? Any ideas what could it be and how to fix it are very welcome.

brk0_0 commented on 2017-03-08 11:40 (UTC) (edited on 2017-03-08 11:40 (UTC) by brk0_0)

When starting package: Error on file "~/.cache/pacaur/cerebro/src/cerebro.desktop": No such file or directory

maximbaz commented on 2017-03-04 11:35 (UTC)

The bug is fixed in 0.2.7, the package is working again!

maximbaz commented on 2017-02-22 15:15 (UTC)

Update: I do reproduce the bug, it is tracked with:

maximbaz commented on 2017-02-22 14:38 (UTC)

@gerson you are likely hitting The developer is asking those who can reproduce this issue to help him debug and fix it, and there is also a workaround available. I can't reproduce it though, it works fine for me.

gerson commented on 2017-02-22 14:34 (UTC)

Is it working? For me it shows only a white rectangle on the screen.