Package Details: octopi 0.9.0-1

Git Clone URL: https://aur.archlinux.org/octopi.git (read-only)
Package Base: octopi
Description: A powerful Pacman frontend using Qt libs
Upstream URL: http://octopiproject.wordpress.com
Licenses: GPL2
Conflicts: octopi-git, octopi-kde-git
Provides: octopi-kde-git
Submitter: ImNtReal
Maintainer: buzo
Last Packager: buzo
Votes: 260
Popularity: 2.638450
First Submitted: 2013-09-03 23:42
Last Updated: 2018-09-25 13:46

Pinned Comments

kikadf commented on 2018-06-10 06:04

Default build octopi-notifier without knotifications support. To enable edit PKGBUILD, uncomment #USE_NOTIFIER='1'

Latest Comments

1 2 3 4 5 6 ... Next › Last »

egrupled commented on 2018-07-10 16:19

@kikadf can you add qmake environment variables to honor custom buildflags?

To do this adjust every qmake-qt5 command like below:

qmake-qt5 QMAKE_CFLAGS_RELEASE="${CFLAGS}" QMAKE_CXXFLAGS_RELEASE="${CXXFLAGS}" QMAKE_LFLAGS_RELEASE="${LDFLAGS}" octopi.pro

After that it will honor use customized buildflags like CXXFLAGS="-march=native" in /etc/makepkg.conf

kikadf commented on 2018-06-13 17:53

@allevil669: remove from local, the patch is changed, so must download the new version. Sorry I late to push the new PKGBUILD with the new sha.

allevil669 commented on 2018-06-13 17:03

At this time, the file "0002-add-pikaur-support.patch" isn't passing sha256sum verification.

kikadf commented on 2018-06-10 09:46

@windy: first remove all octopi packages, after install the new. I remove the splitted packages, this cause the error.

windy commented on 2018-06-10 09:04

The uprade to 0.9.0 fails:

error: failed to commit transaction (conflicting files)

octopi: /etc/dbus-1/system.d/org.octopi.pacmanhelper.conf exists in filesystem (owned by octopi-pacmanhelper)

octopi: /usr/bin/octopi-cachecleaner exists in filesystem (owned by octopi-cachecleaner)

octopi: /usr/bin/octopi-notifier exists in filesystem (owned by octopi-notifier-qt5)

octopi: /usr/bin/octopi-repoeditor exists in filesystem (owned by octopi-repoeditor)

octopi: /usr/lib/octopi/pacmanhelper exists in filesystem (owned by octopi-pacmanhelper)

octopi: /usr/share/applications/octopi-cachecleaner.desktop exists in filesystem (owned by octopi-cachecleaner)

octopi: /usr/share/applications/octopi-repoeditor.desktop exists in filesystem (owned by octopi-repoeditor)

octopi: /usr/share/dbus-1/interfaces/org.octopi.pacmanhelper.xml exists in filesystem (owned by octopi-pacmanhelper)

octopi: /usr/share/dbus-1/system-services/org.octopi.pacmanhelper.service exists in filesystem (owned by octopi-pacmanhelper)

octopi: /usr/share/polkit-1/actions/org.octopi.pacman.policy exists in filesystem (owned by octopi-pacmanhelper)

Errors occurred, no packages were upgraded.

kikadf commented on 2018-06-10 06:04

Default build octopi-notifier without knotifications support. To enable edit PKGBUILD, uncomment #USE_NOTIFIER='1'

Xwang commented on 2018-06-04 22:16

I can confirm that b9654265f915fad6b70606852bbac6e8bcd7138a solves the issue. Can you update the PKGBUILD to use that release, please?

kikadf commented on 2018-06-04 06:52

@Xwang: which version of octopi? Try the latest git version, I think this is the Qt-5.11 build error what is fixed in b9654265f915fad6b70606852bbac6e8bcd7138a.

Edit in PKGBUILD: _gitcommit="52e111f5ab53b5b60ac06ca1cd47c70e0aced435" to _gitcommit="b9654265f915fad6b70606852bbac6e8bcd7138a"

Xwang commented on 2018-06-04 05:58

It does not compile!

In file included from /usr/include/qt/QtCore/qhashfunctions.h:44,
                 from /usr/include/qt/QtCore/qlist.h:47,
                 from /usr/include/qt/QtCore/qvariant.h:45,
                 from /usr/include/qt/QtCore/QVariant:1,
                 from build/ui_transactiondialog.h:12,
                 from src/transactiondialog.h:23,
                 from src/transactiondialog.cpp:20:
/usr/include/qt/QtCore/qstring.h:83:7: note: forward declaration of ‘class QRegularExpression’
 class QRegularExpression;
       ^~~~~~~~~~~~~~~~~~
make: *** [Makefile:1551: build/transactiondialog.o] Error 1

kikadf commented on 2018-06-03 13:41

@jmvazquezes: don't be write only. The symbolic link is not a solution.