Arch Linux User Repository

@Rhinoceros, yes, the pkgrel is important, but what I meant by "it doesn't really matter" is that because VCS packages update the pkgver using the pkgver() function, and there is a possibility of there being newer commits when you're building the package than when the pkgrel was bumped, and if so, the pkgrel gets reset back to 1, IIRC.

Hence, in my experience while working with VCS packages, pkgrel has frequently never worked as intended in VCS packages, especially with AUR helpers.

@mistermee yes, there's not a clear source for the bug that I can see.

The pkgrel can be important because upgrade notifiers will report that there are pending updates when there actually aren't. But having said that, it looks like it was a bug in yay. makepkg builds -2 perfectly fine. I had to manually clean out its cache to get yay to build properly 🤷

@Rhinoceros, I am using Plasma, yes, but I'm not sure if something is up with KDE, we've gone from Plasma 5 to 6, and from 6 to 6.3, soon to be 6.4 now. It is possible, but the rest of the applets are fine, I still can see a tooltip for KeepassXC and the like, for example. It's only caffeine-ng that doesn't have the tooltip.

Hmm, as for the versioning, does sudo pacman -Qi caffeine-ng-git show the descriptions for the optdepends? If yes, then the specific pkgrel doesn't really matter. In my experience, fiddling around with the pkgrel for -git packages has never worked very well.

Sorry, I edited while you were writing. I tested downgrading a few packages, but they didn't help. Perhaps KDE? Thanks again for your comments.

EDIT: and thanks for fixing the versioning... but it still builds as 4.2.0.r45.g8318401-1 for me?

@Rhinoceros, the versioning was probably due to me trying to figure out why the tooltip wasn't appearing and building and rebuilding the package attempting to fix it by trying different things. Sorry about that, it should be fixed now.

I'm not quite sure about what exactly is wrong either, upstream hasn't moved much, and neither has libayatana, frankly. Both of these projects are very stable and code is almost frozen. Libayatana has also been deprecated and they recommend moving to libayatana-appindicator-glib, but that probably isn't relevant to our problem here. The only thing I can think of is something changing with GTK and PyGobject, but that's a little bit beyond me.

Thanks @mistermee for the detailed reply. Now I think about it more, I think you are right, and it's not a packaging issue of this package. It's not an upstream change though, because I have only ever had 4.2.0.r45.g8318401-1 installed. Presumably it's one of the dependencies then?

Thanks for adding the descriptions.

I'm not exactly sure what's going on with the versioning here though. The new AUR version is supposedly 4.2.0.r47.g835de4c-2, but when I makepkg, it uses the latest commit upstream, which is still only 4.2.0.r45.g8318401. You can probably just revert to 4.2.0.r45.g8318401, but with pkgrel=2.

EDIT: I've gone through and downgraded dependencies that have been recently upgraded. This comprised libayatana-appindicator and python-setproctitle. python-click was also recently upgraded, but I don't think that could be relevant. I restarted, and this did not fix it. pactree caffeine-ng-git shows a massive amount of full (recursive) dependencies; too many to easily go through for me, unless we write a short script. Are you using KDE Plasma? That could be another thing that was updated and broke it. FWIW my Nextcloud indicator's tooltip is fine.

@Rhinoceros, I could reproduce your issue, however, I heavily doubt this is a packaging issue, I've made very minimal changes over the time that this could have gone from showing to not showing. However, this is a -git package. It tracks the latest changes to the git repository upstream, even if they are not ready to be shipped as a stable release. It could be related to that, or it could be related to changes in PyGObject, or changes in libayatana.

I have added the descriptions now.

This being a -git package, it tracks any dependency changes that may happen in the main branch, and the dependencies have changed since the last stable release, at least in the main branch and in relation to Arch packages themselves. I am following the upstream list of dependencies in the README.md and the meson.build files.

I used to get a tooltip when hovering over the icon in the tray (in KDE Plasma), which showed what was causing inhibition. It doesn't seem to show any more. I'm not sure if this is a packaging issue. I did install the optdepends libindicator-gtk3 and libappindicator-gtk3 then restarted, but that did not help.

Also, could you please include a description of each optdepends? Further, the stable package has slightly different depends/optdepends. Is there a reason for that?

@Senk42, Python recently got a major version upgrade from 3.12 to 3.13, most probably either caffeine-ng-git is still linked to Python 3.12 or python-ewmh and python-pulsectl are. You can manually check this by going to /usr/lib/python3.12/site-packages/ and seeing what's there.

To rebuild whatever AUR package is still there under python 3.12, if you're using yay or paru as your AUR helper, you can do [yay or paru, whichever you're using] -S --rebuild $(sudo pacman -Qqo /usr/lib/python3.12/site-packages/), if you aren't using paru or yay, then you can uninstall the AUR package that's linked to Python 3.12 and reinstall it.

Getting this again, I thought this was fixed but I have memory issues.

meson.build:24:15: ERROR: python3 is missing modules: ewmh, pulsectl