Package Details: caffeine-ng 3.4.2-2

Git Clone URL: (read-only)
Package Base: caffeine-ng
Description: Status bar application able to temporarily inhibit the screensaver and sleep mode.
Upstream URL:
Keywords: caffeine powersaving screensaver
Licenses: GPL3
Conflicts: caffeine, caffeine-bzr, caffeine-oneclick, caffeine-systray
Provides: caffeine, caffeine-bzr, caffeine-oneclick, caffeine-systray
Replaces: caffeine-oneclick, caffeine-systray
Submitter: WhyNotHugo
Maintainer: WhyNotHugo
Last Packager: WhyNotHugo
Votes: 100
Popularity: 0.409008
First Submitted: 2014-10-19 05:26
Last Updated: 2018-08-06 20:34

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

WhyNotHugo commented on 2017-01-19 20:04

@punk0x29a Please read the pinned post.

punk0x29a commented on 2017-01-19 18:22

pkg_resources.DistributionNotFound: The 'caffeine-ng==3.3.8' distribution was not found and is required by the application
That's what I get now. Previously I fixed the problem by editing requirements, but now that's something different ( I guess...)

PhotonX commented on 2017-01-18 19:19

Ok, I got the point. In my case it was enough to rebuild caffeine-ng to make it work again. On another system I had to rebuild a dependency (ewmh) as well. In the latter case indeed rebuilding caffeine-ng wouldn't help, in the former it would.

WhyNotHugo commented on 2017-01-18 14:35

The setups in question have python pckages pointing to an absent python, and not accesible by the default python.
You might not want to call them broken (it's semantics and poorly relevant), but the rest of the point stands; pushing the pkgrel won't rebuild dependencies. Users should have rebuilt python packages during the python36 update. TBH, I think this should have been an Arch announcement, since it affected too many users/packages.

I've just pinned that comment helping them do that because it's relevant here, but there's no way to push a fix to affected users.

PhotonX commented on 2017-01-18 07:54

What do you mean by "broken setups"? I don't consider my setup broken. :) Isn't a rebuild required for everybody after python is updated?

Concerning the warning: What does

grep -R "$(pwd)/src" pkg/

return if you run in the build directory?

WhyNotHugo commented on 2017-01-18 06:28

> WARNING: Package contains reference to $srcdir.

Not sure how to deal with that. Any hints?

WhyNotHugo commented on 2017-01-18 06:27

> why don't you just bump the revision if you realize that a rebuild is necessary?

A rebuild of dependencies is necessary only for users with broken setups. Pushing the pkgrel won't rebuild dependencies, and would trigger rebuilds for users who don't need it.

PhotonX commented on 2017-01-17 21:39

Makepkg reports:

WARNING: Package contains reference to $srcdir.


Also, why don't you just bump the revision if you realize that a rebuild is necessary?

WhyNotHugo commented on 2017-01-08 19:54


Please understand that that specific command fixed YOUR broken setup, and it's not a universal fix.

sergey.orloff commented on 2017-01-08 18:55

A big thank you to @hobarrera! Hi all! Helped here it is:
sudo pacman -R python-ewmh python-xlib caffeine-ng && sudo pacman -S python-docopt python-setproctitle python-wheel python-xlib && yaourt -S python-ewmh caffeine-ng