Package Details: darkman 1.5.4-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://darkman.whynothugo.nl/
Keywords: dark desktop light mode sundown sunrise
Licenses: ISC
Submitter: whynothugo
Maintainer: whynothugo
Last Packager: whynothugo
Votes: 16
Popularity: 0.24
First Submitted: 2020-12-14 21:11 (UTC)
Last Updated: 2023-03-02 16:02 (UTC)

Latest Comments

1 2 Next › Last »

whynothugo commented on 2023-05-25 14:17 (UTC) (edited on 2023-05-25 14:17 (UTC) by whynothugo)

If someone wants to co-maintain this, I'd appreciate it. I don't have access to an Arch machine these days so it's a bit time consuming to properly test out small fixes to the PKGBUILD.

CodingCellist commented on 2023-05-25 12:15 (UTC)

N.B. The key mentioned in the comments below expired on 2022-06-17, and so doesn't work for the current release. Instead, the following key should be imported:

$ gpg --recv-keys 7880733B9D062837
gpg: key 0x7880733B9D062837: public key "Hugo Osvaldo Barrera <hugo@whynothugo.nl>" imported

Which seems to be whynothugo's current PGP key.

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.

1 2 Next › Last »