Package Details: zandronum-hg r10948+.83b6cd3bc9e6+-1

Git Clone URL: https://aur.archlinux.org/zandronum-hg.git (read-only, click to copy)
Package Base: zandronum-hg
Description: OpenGL ZDoom port with Client/Server multiplayer. (Development branch checkout)
Upstream URL: https://zandronum.com
Licenses: custom
Conflicts: zandronum-dev
Submitter: sanerb
Maintainer: MrSoup678
Last Packager: MrSoup678
Votes: 4
Popularity: 0.000000
First Submitted: 2016-09-13 11:18 (UTC)
Last Updated: 2022-11-19 16:07 (UTC)

Pinned Comments

sanerb commented on 2016-09-13 19:27 (UTC) (edited on 2017-09-01 22:54 (UTC) by sanerb)

# Bug reports can be filed at https://bugs.square-r00t.net/index.php?project=3 # News updates for packages can be followed at https://devblog.square-r00t.net (If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to https://devblog.square-r00t.net/rss/?category=aur in your favourite RSS reader.) Note that you should still use the AUR web interface for flagging packages as out-of-date if a new version is released; the aforementioned bug tracker is to aid in issues with building/packaging/the PKGBUILD formats/etc. specifically. GPG signature "errors" are explained here: https://devblog.square-r00t.net/articles/a-note-on-using-gpg-signatures-in-pkgbuilds Please read; it's not a bug. Thanks!

Latest Comments

1 2 Next › Last »

gustavo6046 commented on 2023-08-24 03:15 (UTC)

The oatch that is causing GPG problems for everyone may not be needed anymore all along. The fix it implements is already present in the original Zandronum code.

dxcvvxd commented on 2023-03-30 17:36 (UTC) (edited on 2023-03-30 17:37 (UTC) by dxcvvxd)

just a warning: i dont know how to make codeblocks there (first time commenting in the aur) it cant verify the signature of the fix_unsafe_print file

[dxc@vxd zandronum-hg]$ makepkg -sirc ==> Making package: zandronum-hg r10948+.83b6cd3bc9e6+-1 (Thu 30 Mar 2023 08:28:09 PM MSK) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Cloning zandronum hg repo... requesting all changes adding changesets adding manifests adding file changes added 10982 changesets with 59067 changes to 4543 files new changesets cc9165005bbc:2ca40fbf0e4d -> Found LICENSE -> Found zandronum-hg.launcher -> Found zandronum-hg-server.launcher -> Found zandronum-hg.png -> Found zandronum-hg.desktop -> Found zandronum-hg.launcher.sig -> Found zandronum-hg-server.launcher.sig -> Found LICENSE.sig -> Found zandronum-hg.png.sig -> Found zandronum-hg.desktop.sig -> Found fix_unsafe_printf.patch -> Found fix_unsafe_printf.patch.sig ==> Validating source files with sha512sums... zandronum ... Skipped LICENSE ... Passed zandronum-hg.launcher ... Passed zandronum-hg-server.launcher ... Passed zandronum-hg.png ... Passed zandronum-hg.desktop ... Passed zandronum-hg.launcher.sig ... Skipped zandronum-hg-server.launcher.sig ... Skipped LICENSE.sig ... Skipped zandronum-hg.png.sig ... Skipped zandronum-hg.desktop.sig ... Skipped fix_unsafe_printf.patch ... Passed fix_unsafe_printf.patch.sig ... Skipped ==> Verifying source file signatures with gpg... zandronum-hg.launcher ... Passed zandronum-hg-server.launcher ... Passed LICENSE ... Passed zandronum-hg.png ... Passed zandronum-hg.desktop ... Passed fix_unsafe_printf.patch ... FAILED ==> ERROR: One or more PGP signatures could not be verified! [dxc@vxd zandronum-hg]$

grcancelliere commented on 2021-11-26 22:11 (UTC)

The new mercurial repo also has this commit so this package can add fmodex as a dependency, rather than downloading version 4.24.16 from Zandronum.

micwoj92 commented on 2020-09-08 01:25 (UTC)

It is because bitbucket no longer hosts mercurial repositories

sanerb commented on 2020-04-03 18:19 (UTC)

so just a heads-up, it looks like either i'm on a really bad connection or, more likely as i've tried it several times now, their repo is fucked:

$ makepkg
==> Extracting sources...
  -> Creating working copy of zandronum hg repo...
pulling from /opt/dev/arch/zandronum-hg/zandronum
searching for changes
no changes found
abort: data/dumb/src/core/duhlen.c.i@1c45222b99a9: no match found!
abort: data/dumb/src/core/atexit.c.i@001b4e1c5599: no match found!
==> ERROR: Failure while updating working copy of zandronum hg repo
    Aborting...

$ cd src/zandronum
$ hg verify
(...)
checked 10075 changesets with 12899 changes to 4530 files                                                                                                                                                                                     
1521 warnings encountered!
hint: run "hg debugrebuildfncache" to recover from corrupt fncache
45355 integrity errors encountered!
(first damaged changeset appears to be 0)

welp.

sanerb commented on 2017-12-14 16:05 (UTC)

@maxiefou-

indeed there is! because 3.0 didn't hit stable until september of this year and i totally didn't realize it! :)

i've added 3.0 stable to the AUR: https://aur.archlinux.org/packages/zandronum/

it packages but i haven't tested runtime yet. mind testing for me?

maxlefou commented on 2017-12-14 08:05 (UTC)

Is there any rational reason of why there's no more stable version of zandronum 3.0 ? This one here is too much updated for using it in multiplayer using doomseeker and zandronum2 is too much outdated...

sanerb commented on 2017-06-19 14:46 (UTC)

hi @fauxmight- can you clarify the need for this? i just built using gcc 7.1.1 (stock arch gcc-multilib) with no fatal errors, nor do i see 4.9 mentioned at https://wiki.zandronum.com/Compiling_Zandronum_on_Linux#Arch_Linux. if you're receiving an error during build, please post the error.

fauxmight commented on 2017-06-19 14:21 (UTC)

Please add gcc49 as a dependency.

sanerb commented on 2016-09-13 19:27 (UTC) (edited on 2017-09-01 22:54 (UTC) by sanerb)

# Bug reports can be filed at https://bugs.square-r00t.net/index.php?project=3 # News updates for packages can be followed at https://devblog.square-r00t.net (If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to https://devblog.square-r00t.net/rss/?category=aur in your favourite RSS reader.) Note that you should still use the AUR web interface for flagging packages as out-of-date if a new version is released; the aforementioned bug tracker is to aid in issues with building/packaging/the PKGBUILD formats/etc. specifically. GPG signature "errors" are explained here: https://devblog.square-r00t.net/articles/a-note-on-using-gpg-signatures-in-pkgbuilds Please read; it's not a bug. Thanks!

1 2 Next › Last »