Package Details: darkman 1.3.1-1

Git Clone URL: https://aur.archlinux.org/darkman.git (read-only, click to copy)
Package Base: darkman
Description: Framework for dark-mode and light-mode transitions on Linux desktop.
Upstream URL: https://gitlab.com/whynothugo/darkman
Keywords: dark desktop light mode sundown sunrise
Licenses: ISC
Submitter: whynothugo
Maintainer: whynothugo
Last Packager: whynothugo
Votes: 6
Popularity: 0.60
First Submitted: 2020-12-14 21:11 (UTC)
Last Updated: 2022-04-19 14:56 (UTC)

Latest Comments

jarohen commented on 2022-04-04 09:31 (UTC)

Grand, thanks @whynothugo :)

whynothugo commented on 2022-03-15 18:53 (UTC)

gpg --recv-keys 13FF264E91839686966CA2AC388ADF1E2EEA7F1A work for me with these gpg settings:

keyserver pgp.mit.edu
keyserver hkp://keyserver.ubuntu.com
keyserver-options auto-key-retrieve

jarohen commented on 2022-03-15 09:31 (UTC)

@whynothugo both the original comment and your suggestion fail for me, I'm afraid:

gpg --recv-keys 13FF264E91839686966CA2AC388ADF1E2EEA7F1A
gpg: keyserver receive failed: No data

I can receive other keys, so I don't think it's a temporary issue.

Could you let us know which key server you've sent the key to?

Cheers,

James

whynothugo commented on 2022-01-12 00:01 (UTC)

@corecode Nope, it should resolve fine with the defaults, AFAIK.

Can you try gpg --recv-keys 13FF264E91839686966CA2AC388ADF1E2EEA7F1A? Maybe the keyserver was down when you tried?

corecode commented on 2021-12-31 05:45 (UTC) (edited on 2021-12-31 05:45 (UTC) by corecode)

yay complains:

:: PGP keys need importing:
 -> 13FF264E91839686966CA2AC388ADF1E2EEA7F1A, required by: darkman
==> Import? [Y/n] 
:: Importing keys with gpg...
gpg: keyserver receive failed: No data
 -> problem importing keys

Do I need to configure a specific keyserver?

whynothugo commented on 2021-09-27 15:18 (UTC)

@drews54 Thanks for pointing this out, fixed. Looks like I had messed up cache locally, and had a hard time actually reproducing the failure.

@MrHritik Should probably be mentioned upstream, since that's a limitation of geoclue itself. It's still not 100% clear what geoclue expects of applications/agents.

drews54 commented on 2021-09-27 13:36 (UTC)

Bug: When building, throws a cd: no such file or directory error. Fix: Change lines 17 and 28 cd "$pkgname-v$pkgver" to cd "$pkgname".

MrHritik commented on 2021-09-12 21:17 (UTC)

Not sure if it's mentioned, but I had to run /usr/lib/geoclue-2.0/demos/agent in order for geoclue to work here.

whynothugo commented on 2021-05-26 14:45 (UTC)

I tried rebuilding in a clean chroot (without python-wheel) and it builds fine.

TheStroyer commented on 2021-05-26 13:22 (UTC)

At first it didn't. I tried it once more and now both makepkg and yay work fine. I didn't even redownload the sources. Maybe the reboot after installing python-wheel did the thing. Do you think python-wheel should be added to the dependencies?

whynothugo commented on 2021-05-26 12:00 (UTC)

@TheStroyer

Does using makepkg directly work? I'm not fully certain what's going into an infinite loop here.

TheStroyer commented on 2021-05-24 17:24 (UTC)

Installation gets stuck for me. It gives the warning "WARNING: The wheel package is not available.". Installing python-wheel gets rid of the warning, but it still gets stuck at the build() stage. The yay output (with python-wheel installed) can be found here: https://gist.github.com/fwSmit/2a5d5db13502ef78713e7dcf972ff8f7. I pressed ^C after waiting for a bit to get a traceback.

whynothugo commented on 2021-02-03 09:02 (UTC)

Updated, thanks!

I haven't quite figured out how to create a clean chroot with all dependencies easily, do you have any reference for this?

djmattyg007 commented on 2021-02-03 04:49 (UTC)

When I try to build 0.1.4 in a clean chroot, I get an error saying pip isn't installed. I created a gist with the error:

https://gist.github.com/djmattyg007/0d4ef199bd4db79de0ced2258dfc99ea