Package Details: octopi 0.17.0-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://github.com/aarnt/octopi
Licenses: GPL-2.0-or-later
Conflicts: alpm_octopi_utils
Submitter: ImNtReal
Maintainer: xiota
Last Packager: xiota
Votes: 1637
Popularity: 34.44
First Submitted: 2013-09-03 23:42 (UTC)
Last Updated: 2025-02-18 19:38 (UTC)

Dependencies (21)

Required by (0)

Sources (2)

Latest Comments

« First ‹ Previous 1 .. 26 27 28 29 30 31 32 33 34 35 36 .. 40 Next › Last »

ImNtReal commented on 2015-11-13 14:05 (UTC)

Try octopi-notifier-noknotify

pmattern commented on 2015-11-12 21:51 (UTC)

If Octopi notifier gets compiled with DEFINES += KSTATUS enabled in ./notifier/octopi-notifier/octopi-notifier.pro it needs package knotifications at runtime, too. Now that package octopi-notifier-kde4 was dropped it should better be removed as optional dependency of package octopi. That aside I'm not sure whether it's that good to provide Octopi notifier with the said switch in octopi-notifier.pro enabled only. If notifier compiled that way gets run in panel plugins implementing the old System Tray Protocol its context menu comes up as a regular window and launching the main GUI by double-click doesn't work. In plugins implementing SNI the context menu comes up as expected but opening the GUI by double clicking doesn't work either, no matter whether or not the said switch is enabled. If compiled with the switch disabled and run in a plugin implementing System Tray Protocol everything is fine. Also, I'm not that sure about the meaning of that switch any more. First I thought it was needed to enable support of SNI. But apparently this doesn't apply any longer if Octopi gets compiled against Qt 5.5. So not really sure what's the best thing to do. But I'd tend to say it's better two provide a version with and without the switch enabled again or even only one with the switch disabled. If you should decide to provide both variants of notifier again, I'd suggest to name the one with the switch enabled something like octopi-notifier-sni as the usage isn't limited to KDE any longer.

AnAkkk commented on 2015-10-28 00:02 (UTC)

When using octopi-notifier on Plasma 5 and when there are updates available, plasmashell CPU usage keeps increasing over time and goes to 100% for some reason. Killing octopi-notifier solves it, and starting it again makes plasmashell goes back to 100%.

FiyreWyrkz commented on 2015-10-21 19:53 (UTC)

It has been commented previously, however, I shall mention again. This package should likely only provide one of the octopi-notifier packages as there becomes a conflicting issue when trying to build and install the entire package. Would seem logical to separate the plasma 4 stuff. pkgname=('octopi' 'octopi-notifier' 'octopi-notifier-kde4' 'octopi-repoeditor' 'octopi-cachecleaner') package_octopi-notifier() {... conflicts=('octopi-notifier-qt4' 'octopi-notifier-kde' 'octopi-notifier-kde4') ... package_octopi-notifier-kde4() ... conflicts=('octopi-notifier' 'octopi-notifier-kde') ...

kikadf commented on 2015-09-28 14:27 (UTC)

@acidicX, after build, aura saves somewhere the builded binaries? yaourt saved those in /tmp/yaourt-tmp-$USER/ After build, just cd /tmp/yaourt-tmp-$USER/ && pacman -U "wanted binaries" You can install only one octopi-notifier (default or kde version).

ImNtReal commented on 2015-09-28 13:47 (UTC)

This is why I created octopi-notifier-qt4 as a separate package originally. I think I might try that, again.

acidicX commented on 2015-09-27 10:54 (UTC)

aura also says octopi-notifier-kde and octopi-notifier are in conflict, is there a way to resolve this?

piedro commented on 2015-09-03 12:24 (UTC)

Thx - I could install now again. Cheers, p.

ImNtReal commented on 2015-08-26 16:19 (UTC)

@piedro, try clearing you src directory.

piedro commented on 2015-08-26 15:29 (UTC)

this doesn't work anymore, it says something about "Reversed (or previously applied) patch detected!" and whatever I answer it will not install anymore. So I removed octopi but reinstallation shows the same result. What to do here or would you fix it?

« First ‹ Previous 1 .. 26 27 28 29 30 31 32 33 34 35 36 .. 40 Next › Last »