Package Details: octopi 0.16.2-2

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://github.com/aarnt/octopi
Licenses: GPL-2.0-or-later
Conflicts: alpm_octopi_utils
Submitter: ImNtReal
Maintainer: xiota
Last Packager: xiota
Votes: 1601
Popularity: 32.71
First Submitted: 2013-09-03 23:42 (UTC)
Last Updated: 2024-12-24 03:40 (UTC)

Dependencies (20)

Required by (0)

Sources (2)

Latest Comments

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 39 Next › Last »

rushaur commented on 2016-08-30 10:51 (UTC)

Am wondering if there is an elegant way to build only pkgs I need when updating. I only need octopi, octopi-notifier-qt5 (depends on pacmanhelper), but all of them are being built so I have always to change the pkgbuild when updating?! Octopi-notifier-qt5 works fine in my GTK based DE (XFCE), so IMHO the qt4 version should be dropped. May be considering separate pkgbuilds?

oi_wtf commented on 2016-08-29 18:34 (UTC)

qt4 should be added to makedepends, since qmake-qt4 is used in the PKGBUILD.

davidmcinnis commented on 2016-08-24 20:59 (UTC)

Additional dependency: knotifications

Bobses commented on 2016-08-24 13:55 (UTC) (edited on 2016-08-24 13:56 (UTC) by Bobses)

Update works great with pacaur. So, goodbye yaourt!

oxalin commented on 2016-08-22 19:17 (UTC)

The problem here is that notifier-frameworks is conflicting with other notifiers. They are built all at once from the octopi package and pacman doesn't make a distinction if they are going to be installed or not. As reported by others, updating from octopi 0.8.1 to 0.8.3 will fail if the old notifier was installed. Using "replaces" should allow to make a transparent transition from octopi-notifier to octopi-frameworks, but, as of now, this is only used by sysupgrades (see Replaces https://www.archlinux.org/pacman/PKGBUILD.5.html). Brainstorming here: - Maybe notifiers should have their own PKGBUILD files as a workaround. - Otherwise, we should make sure the notifier-frameworks (which, by its name, should be a requirement for any notifier as a base layer upon which the notifiers are built) contains only files that are common to notifiers. It may not be possible for now (no lib, only a single application file). - Finally, from the usecases described ("If you use kde5, install only notifier-frameworks..."), why would we need a "-frameworks" and a "-qt5" if both run with qt5?

mozo commented on 2016-08-22 11:09 (UTC)

kikadf I don't want to install anything. I just update my Octopi installation and thi error occurs. yaourt -Syau, that's all.

philo commented on 2016-08-21 17:59 (UTC)

I doubt whether yaourt will ever solve its problem. Time for me to ditch yaourt and adopt pacaur.

ImNtReal commented on 2016-08-20 13:30 (UTC)

@kikadf, I suspect the confusion comes from when you try to install octopi via yaourt. It will try to install everything from the split package at once. It doesn't seem to have a method developed to allow you to select a subset of the packages.

kikadf commented on 2016-08-20 12:50 (UTC)

Don't undesrtand your problem. Why do you want to install notifier-frameworks and notifier-qt*? First remove old notifier-0.8.1. (conflict with new notifiers) If you use kde5, install only notifier-frameworks. If you use other, but you have qt5, install only notifier-qt5. If you use other, but you have qt4, install only notifier-qt4.

mozo commented on 2016-08-20 12:43 (UTC)

Same error here: octopi-notifier-frameworks and octopi-notifier-qt4 are in conflict

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 39 Next › Last »