Package Details: chocolate-doom 3.1.0-1

Git Clone URL: https://aur.archlinux.org/chocolate-doom.git (read-only, click to copy)
Package Base: chocolate-doom
Description: Historically-accurate Doom, Heretic, Hexen, and Strife ports.
Upstream URL: http://www.chocolate-doom.org/
Licenses: GPL2
Conflicts: chocolate-common, chocolate-heretic, chocolate-hexen, chocolate-strife
Replaces: chocolate-common, chocolate-heretic, chocolate-hexen, chocolate-strife
Submitter: None
Maintainer: chungy
Last Packager: chungy
Votes: 60
Popularity: 0.61
First Submitted: 2006-07-30 06:27 (UTC)
Last Updated: 2024-08-03 17:28 (UTC)

Dependencies (8)

Required by (2)

Sources (2)

Pinned Comments

chungy commented on 2017-01-18 02:40 (UTC)

You'll either need to import fraggle's public key (available here: https://soulsphere.org/gpg-key.txt or https://keybase.io/fraggle), or run makepkg with --skippgpcheck

Latest Comments

1 2 3 Next › Last »

jsx commented on 2022-11-10 11:47 (UTC)

Hmm, is this project still alive? Anybody who can help out configuring the background music? I set up some arch linux machines and on none the music is working out of the box, although it installs timidity as a dependency.

jsx commented on 2022-11-01 20:55 (UTC)

Thanks for providing this great application. Since a while I don't have any background sound and get the message "Error loading midi: Couldn't open timidity.cfg". When setting timidity_cfg_path in the config file to a valid timidity.cfg, it says "Error loading midi: Couldn't open /tmp/timidity.cfg" although I set the path to something else than /tmp/timidity.cfg (but problem persists when setting it to /tmp/timidity.cfg, too). So far I think it's my fault and like to ask for help here. When copying a valid timidity.cfg to /tmp/timidity.cfg, chocolate doom will delete it and display "Error loading midi: Couldn't open /tmp/timidity.cfg", at least for this I'm sure it's a bug.

chungy commented on 2020-11-16 10:10 (UTC)

Instead of being rude, maybe actually check what you're saying.

$ gpg --verify chocolate-doom-3.0.1.tar.gz.asc 
gpg: assuming signed data in 'chocolate-doom-3.0.1.tar.gz'
gpg: Signature made Wed 24 Jun 2020 08:22:20 PM PDT
gpg:                using RSA key 6D2C117E0310664497AA9546F6C2EE9C23354344
gpg: Good signature from "Simon Howard <fraggle@soulsphere.org>" [unknown]
gpg:                 aka "Simon Howard <fraggle@gmail.com>" [unknown]

in the PKGBUILD:

validpgpkeys=('6D2C117E0310664497AA9546F6C2EE9C23354344')

terrytuden114 commented on 2020-11-16 07:15 (UTC)

This doesn't work. Why can't you people just use a normal ass key? Jesus christ.

No, fraggle's public key DOESN'T work, and neither do any of the keys it tells me to import.

Stop posting trash to the aur maybe.

SpacingBat3 commented on 2020-05-28 11:47 (UTC)

I successfully built package with AARCH64 on Manjaro ARM (Raspberry Pi 4 model B), could you update PKGBUILD and add this arch so some package managers like pamac would recognise it as compatible?

chungy commented on 2020-01-20 06:42 (UTC)

You need to import the appropriate public key.

mreutman commented on 2020-01-20 05:34 (UTC)

Public key is still invalid as of January 2020.

==> Verifying source file signatures with gpg...
    chocolate-doom-3.0.0.tar.gz ... FAILED (unknown public key F6C2EE9C23354344)
==> ERROR: One or more PGP signatures could not be verified!

Morganamilo commented on 2018-10-25 19:57 (UTC)

PGP keys are still missing from the srcinfo though.

chungy commented on 2018-10-25 19:51 (UTC)

I don't seem to replicate the issue, it was probably just a temporary problem. Updating it to HTTPS anyway seems like a good idea though, thanks.

1 2 3 Next › Last »