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: 227
Popularity: 3.668724
First Submitted: 2013-09-03 23:42
Last Updated: 2016-11-02 17:54

Dependencies (19)

Required by (1)

Sources (2)

Pinned Comments

ImNtReal commented on 2017-02-08 19:06

Please, do not use yaourt to install this package. It does not handle conflicts inside of a split package correctly. This can be installed by building manually, or by using pacaur, and specifying one of the octopi-notifier- packages.

Latest Comments

ImNtReal commented on 2017-02-08 19:06

Please, do not use yaourt to install this package. It does not handle conflicts inside of a split package correctly. This can be installed by building manually, or by using pacaur, and specifying one of the octopi-notifier- packages.

D4v2z commented on 2017-02-08 18:56

@adomas Install : https://aur.archlinux.org/packages/octopi-git/

adomas commented on 2017-02-08 00:00

I have this issue which @Aeronaelius mentioned. Using yaourt fails to install:
==> Continue installing octopi ? [Y/n]
==> [v]iew package contents [c]heck package with namcap
==> ---------------------------------------------------
==> y

loading packages...
resolving dependencies...
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
==> WARNING: Your packages are saved in /tmp/yaourt-tmp-adomas

Aeronaelius commented on 2017-01-18 11:44

@ImNtReal
Building manually gives the same error. There is a conflict in the PKGBUILD file of 'octopi':

pkgname=('octopi' 'octopi-pacmanhelper' 'octopi-notifier-qt5' 'octopi-notifier-frameworks' 'octopi-repoeditor' 'octopi-cachecleaner')

It builds both the 'octopi-notifier-qt5' and the 'octopi-notifier-frameworks' packages and those two are in conflict (look at their respective PKGBUILD files).

I successfully installed 'octopi' with yaourt by editing its PKGBUILD file and removing any mention of 'octopi-notifier-qt5'. This way it only builds 'octopi-notifier-frameworks'. The conflict error is no longer triggered.

I think it would be best if the PKGBUILD asks the user whether to install 'octopi-notifier-qt5' or 'octopi-notifier-frameworks'.

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.

All comments