Package Details: octopi 0.16.2-1

Git Clone URL: https://aur.archlinux.org/octopi.git (read-only, click to copy)
Package Base: octopi
Description: A powerful Pacman frontend using Qt libs
Upstream URL: https://tintaescura.com/projects/octopi
Licenses: GPL-2.0-or-later
Conflicts: octopi-notifier
Provides: octopi-cachecleaner, octopi-notifier, octopi-repoeditor
Submitter: ImNtReal
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 1564
Popularity: 33.98
First Submitted: 2013-09-03 23:42 (UTC)
Last Updated: 2024-06-18 16:53 (UTC)

Dependencies (17)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 39 Next › Last »

dracorp commented on 2016-11-25 08:32 (UTC)

@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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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!

Flobbes commented on 2016-10-20 05:54 (UTC)

I'm having the same problem with the conflicting packages. Luckily the tip from matmoul to manually install after the compilation worked.

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 39 Next › Last »