Package Base Details: freedoom

Git Clone URL: https://aur.archlinux.org/freedoom.git (read-only)
Submitter: None
Maintainer: chungy
Last Packager: chungy
Votes: 69
Popularity: 0.482243
First Submitted: 2006-07-29 16:53
Last Updated: 2017-07-23 02:43

Packages (3)

Latest Comments

sanerb commented on 2017-08-13 08:50

@maxlefou-

chungy does what i do. you need to either disable GPG checking or add the key. i have instructions on how to do either at https://devblog.square-r00t.net/articles/a-note-on-using-gpg-signatures-in-pkgbuilds (to be more accurate, he uses the upstream GPG signatures directly)

just replace every occurrence of "8C004C2F93481F6B" in that post with "99459CE2770037FF5566EB4B8649B37607A08042".

maxlefou commented on 2017-08-08 08:02

Can't compile. PGP public key unknown.
And yes, this package. not deutex, since i have deutex-git installed.

heichblatt commented on 2017-07-22 09:17

According to deutex-devel's AUR page, they will be retiring that package in favor of deutex-git. FreeDOOM works with deutex-git. Please change the dependency.

---
% git diff
diff --git a/PKGBUILD b/PKGBUILD
index c5310c7..0776e4d 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -8,7 +8,7 @@ pkgdesc="Free game based on the Doom engine"
arch=('any')
url="https://freedoom.github.io/"
license=('BSD')
-makedepends=('asciidoc' 'deutex-devel' 'imagemagick' 'python' 'ttf-liberation')
+makedepends=('asciidoc' 'deutex-git' 'imagemagick' 'python' 'ttf-liberation')
source=(https://github.com/$pkgbase/$pkgbase/archive/v$pkgver.tar.gz
https://github.com/$pkgbase/$pkgbase/releases/download/v$pkgver/v$pkgver.tar.gz.asc)
sha512sums=('51e0d5f7ca7c846c556fcba36b0f9c815090bfc76a80200aebd1526291da16b71145fbe254100cc5ad37ffc044d4380ef07b8bd4bdb811f00b9150e7b34dd636'
---

chungy commented on 2017-07-18 23:50

Yes, DeuTex is updated and no longer builds Freedoom 0.11.2. I'll push out a point release only to fix that.

Anonymous comment on 2017-07-18 22:41

I get all the way through and then this happens

deutex -v0 -fullsnd -rate accept -rgb 0 255 255 -doom2 bootstrap/ -iwad -build wadinfo_freedm.txt wads/freedm.wad
E AA95 Invalid option "-fullsnd"
make: *** [Makefile:57: wads/freedm.wad] Error 2

Any idea on how to fix?

gruel commented on 2017-03-19 17:55

Here a little bit longer log. All the dependencies are installed and it it the first time I am seeing this kind of error. I have absolutely no idea of what it is... Thank you to try to help me.

cp freedm/texture1.lmp ../fdmtxtr1.lmp
cp freedm/pnames.lmp ../fdmpname.lmp
make[1]: Leaving directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/lumps/textures'
make -C bootstrap
make[1]: Entering directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/bootstrap'
./bootstrap.py < ../lumps/playpal/playpal-base.lmp > doom2.wad
make[1]: Leaving directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/bootstrap'
echo v0.11.2 > lumps/freedoom.lmp
echo v0.11.2 > lumps/freedm.lmp
scripts/simplecpp -P -DFREEDM < buildcfg.txt | scripts/wadinfo-builder.py -dummy > wadinfo_freedm.txt
rm -f wads/freedm.wad
deutex -v0 -fullsnd -rate accept -rgb 0 255 255 -doom2 bootstrap/ -iwad -build wadinfo_freedm.txt wads/freedm.wad
w PC10 GIF support may go away in the future
scripts/simplecpp -P -DDOOM1 -DULTDOOM < buildcfg.txt | scripts/wadinfo-builder.py -dummy > wadinfo_phase1.txt
rm -f wads/freedoom1.wad
deutex -v0 -fullsnd -rate accept -rgb 0 255 255 -doom2 bootstrap/ -iwad -lumps -patch -flats -sounds -musics -graphics -sprites -levels -build wadinfo_phase1.txt wads/freedoom1.wad
w PC10 GIF support may go away in the future
scripts/simplecpp -P -DDOOM2 < buildcfg.txt | scripts/wadinfo-builder.py -dummy > wadinfo_phase2.txt
rm -f wads/freedoom2.wad
deutex -v0 -fullsnd -rate accept -rgb 0 255 255 -doom2 bootstrap/ -iwad -lumps -patch -flats -sounds -musics -graphics -sprites -levels -build wadinfo_phase2.txt wads/freedoom2.wad
w PC10 GIF support may go away in the future
==> Entering fakeroot environment...
==> Starting package_freedm()...
make -C graphics/text
make[1]: Entering directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/graphics/text'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/graphics/text'
make VERSION=v0.11.2 -C graphics/titlepic
make[1]: Entering directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/graphics/titlepic'
make[1]: Nothing to be done for 'titlepic'.
make[1]: Leaving directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/graphics/titlepic'
make -C lumps/playpal
make[1]: Entering directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/lumps/playpal'
make[1]: 'playpal.lmp' is up to date.
make[1]: Leaving directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/lumps/playpal'
make -C lumps/colormap
make[1]: Entering directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/lumps/colormap'
cp colormap.lmp ../
make[1]: Leaving directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/lumps/colormap'
make -C lumps/genmidi
make[1]: Entering directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/lumps/genmidi'
make[1]: 'genmidi.lmp' is up to date.
make[1]: Leaving directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/lumps/genmidi'
make -C lumps/dmxgus
make[1]: Entering directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/lumps/dmxgus'
make[1]: 'ultramid.ini' is up to date.
make[1]: Leaving directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/lumps/dmxgus'
make -C lumps/textures
make[1]: Entering directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/lumps/textures'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/lumps/textures'
make -C bootstrap
make[1]: Entering directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/bootstrap'
make[1]: 'doom2.wad' is up to date.
make[1]: Leaving directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/bootstrap'
echo v0.11.2 > lumps/freedoom.lmp
echo v0.11.2 > lumps/freedm.lmp
scripts/simplecpp -P -DFREEDM < buildcfg.txt | scripts/wadinfo-builder.py -dummy > wadinfo_freedm.txt
rm -f wads/freedm.wad
deutex -v0 -fullsnd -rate accept -rgb 0 255 255 -doom2 bootstrap/ -iwad -build wadinfo_freedm.txt wads/freedm.wad
w PC10 GIF support may go away in the future
make -C dist man-freedm
make[1]: Entering directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/dist'
sed -e s/freedoom/freedm/ freedoom.adoc > freedm.adoc
a2x -f manpage freedm.adoc
a2x: ERROR: "xsltproc" --stringparam callout.graphics 0 --stringparam navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 "/etc/asciidoc/docbook-xsl/manpage.xsl" "/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/dist/freedm.xml" returned non-zero exit status 5
make[1]: *** [Makefile:3: man-freedm] Error 1
make[1]: Leaving directory '/tmp/yaourt-tmp-gruel/aur-freedoom1/src/freedoom-0.11.2/dist'
make: *** [Makefile:129: freedm.6] Error 2
==> ERROR: A failure occurred in package_freedm().
Aborting...
==> ERROR: Makepkg was unable to build freedoom.

chungy commented on 2017-03-18 22:54

Do you have more of the log to show? I can't really guess what's wrong.

You might also try using clean-chroot-manager ("sudo ccm64 s" to build for instance; also requires deutex-devel to be installed/built in it first). Sometimes weird issues happen with the combination of your installed packages and having a minimum Arch to build instead (that clean-chroot-manager provides) is better.

gruel commented on 2017-03-18 22:34

Cannot compile the package. I got the error:

xsltproc" --stringparam callout.graphics 0 --stringparam navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 "/etc/asciidoc/docbook-xsl/manpage.xsl"

I have docbook-xsl already installed so I do not understand why the installation does not ended properly.

chungy commented on 2017-02-25 09:47

Use "makepkg --skippgpcheck" or import https://keybase.io/chungy/pgp_keys.asc

simona commented on 2017-02-25 07:39

==> Validazione delle firme dei sorgenti con gpg in corso...
v0.11.1.tar.gz ... NON RIUSCITO (chiave pubblica sconosciuta 8649B37607A08042)
==> ERRORE: Una o più firme PGP non possono essere verificate!
==> ERRORE: Makepkg non è riuscito a compilare freedoom.

sanerb commented on 2016-12-30 16:26

this can cause failures in certain build environments.

==> Starting prepare()...
ln: failed to create symbolic link '/tmp/pkgbuild-0/freedoom2/src/freedoom1-0.10.1/freedoom-0.10.1': File exists
==> ERROR: A failure occurred in prepare().

you should either:

1.) have freedoom2, freedoom1, and freedm as totally separate packages

2.) remove the split-packaging and create one "freedoom" package that builds and installs freedoom1, freedoom2, and freedm as a unified package

3.) use ln -sf instead of ln -s (recommended regardless, so multiple iterations of packaging don't fail) (messiest but quickest)

luuuciano commented on 2016-04-21 14:52

What is the difference with freedoom1?

chungy commented on 2014-10-14 16:49

0.9 is out, and there are quite a few upstream changes that can affect packaging, namely Freedoom now supports install targets to install application icons and desktop entries, just making it simpler to launch Freedoom. This package has so far just grabbed the pre-built zips and used those, which works fine, but doing that now misses out on the other benefits.

All the same, I must warn about the caveat: Freedoom's builds are not yet deterministic and there are known ImageMagick subtleties that make a build on Arch differ from the official release (which was built on Debian Wheezy), not in any significant way, but only in how some graphics are dithered. This *might* cause issue in multiplayer ports because of the checksum will not match... there is good cause to continue grabbing the official zips for this reason. I might even suggest copying the dist directory from the source and doing all the other packaging stuff separately.

DavidK commented on 2013-05-22 23:16

Oops, fixed reference to patches.

miffe commented on 2013-05-22 23:05

I get this when building with devtools, use $srcdir instead of ../../

==> Starting prepare()...
/build/PKGBUILD: line 23: ../../patches: No such file or directory

jsteel commented on 2012-10-16 06:30

It is currently a makedepends, are you sure it is needed at run time?

Anonymous comment on 2012-10-16 05:34

deutex-devel - http://aur.archlinux.org/packages.php?ID=8447 - should be listed as a dependency.

breed808 commented on 2012-09-15 14:42

Well, it's building for me just fine, so I'm at a loss to explain the previous build failures.

breed808 commented on 2012-09-08 15:18

Hmm, I'm managed to successfully compile the package today, but the PKGBUILD I used was identical to the one currently here. I'm going to double-check first, and if it's still good I'll unflag the package.

breed808 commented on 2012-08-21 16:58

Package needs updating, as both the problems that Ratfink and miffe described are still occuring.

miffe commented on 2012-04-11 20:56

This package need options=(!makeflags) since it fails to build when -j is >1

Ratfink commented on 2010-12-31 23:48

This package needs to be updated. Since Python is now Python 3, I'm getting lots of syntax errors. All that's needed to fix it, though, is to replace all the
#!/usr/bin/env python
lines with
#!/usr/bin/env python2
and then it would work.

Arkham commented on 2010-08-25 07:13

Url fixed.

Anonymous comment on 2010-08-17 15:52

If a package is broken does that mean it's out of date?

Why isn't there a flag broken button?

Or flag malicious?

Or flag inapropriate?

Anonymous comment on 2010-08-14 19:18

can't build, 404 not found.