Package Details: octopi 0.8.5-2

Git Clone URL: https://aur.archlinux.org/octopi.git (read-only)
Package Base: octopi
Description: A powerful Pacman frontend using Qt5 libs
Upstream URL: http://octopiproject.wordpress.com
Licenses: GPL2
Conflicts: octopi-git
Submitter: ImNtReal
Maintainer: ImNtReal
Last Packager: ImNtReal
Votes: 222
Popularity: 4.906096
First Submitted: 2013-09-03 23:42
Last Updated: 2016-11-02 17:54

Dependencies (19)

Required by (1)

Sources (2)

Latest Comments

ImNtReal commented on 2016-11-26 22:27

@dracorp, yaourt won't work for installing this package. Please, build it manually, or use pacaur. Read previous comments for details on why.

dracorp commented on 2016-11-25 08:32

@ImNtReal
Clean installation of octopi:

yaourt -S octopi
(...)
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: octopi-notifier-frameworks and octopi-notifier-qt5 are in conflict

oi_wtf commented on 2016-11-04 00:42

When building this in a headless environment, it complains about missing GL/gl.h include. So mesa should probably be a makedepend.

FTR, error is:

In file included from /usr/include/qt/QtGui/qopenglcontext.h:60:0,
from /usr/include/qt/QtGui/QtGui:32,
from src/main.cpp:29:
/usr/include/qt/QtGui/qopengl.h:129:21: fatal error: GL/gl.h: No such file or directory
# include <GL/gl.h>
^
compilation terminated.

portaloffreedom commented on 2016-10-25 11:16

I cannot build the package, it gives me the error "c++11 support needed from Qt"

adding this at the bottom of the prepare function fixes it:

echo "CONFIG += c++11" >> notifier/pacmanhelper/pacmanhelper.pro
echo "CONFIG += c++11" >> repoeditor/octopi-repoeditor.pro
echo "CONFIG += c++11" >> cachecleaner/octopi-cachecleaner.pro

I'll leave it here if someone has the same problem

pmarcelll commented on 2016-10-23 11:05

The notifications stopped in the new release, but the bug was fixed in master. Can you update this package as well? Thanks.

ImNtReal commented on 2016-10-21 20:37

After speaking with the developer, I have decided to stop following the Manjaro releases. Please, do not mark the package out of date because of a new Manjaro package.

kikadf commented on 2016-10-21 17:01

No, the developer working for the new features, check the changelog.txt history. He will tagging a release, if the features will be enough stable for a release. Now we use the instable git source as stable... If devs of Manjaro know better than dev of octopi, they should fork octopi, not make FAKE octopi releases...

ImNtReal commented on 2016-10-21 16:24

Because the developer seems to have stopped tagging releases. This is based on the commit Manjaro uses for their 0.8.5 release.

kikadf commented on 2016-10-21 16:08

Don't understand, why do you build instable git version as stable release?
Use octopi-git and alpm-octopi-utils-git pkgnames instead of FAKE pkgver...

:/

z3ntu commented on 2016-10-21 10:59

The package doesn't build in a clean chroot:

==> Building octopi-notifier-frameworks...
Project ERROR: Unknown module(s) in QT: KNotifications

The package knotifications should be included in the makedepends!

All comments