Package Details: zandronum-hg r10074.c11f78a5b028-2

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: sanerb
Last Packager: sanerb
Votes: 4
Popularity: 0.000000
First Submitted: 2016-09-13 11:18
Last Updated: 2020-04-03 18:18

Required by (0)

Sources (15)

Pinned Comments

sanerb commented on 2016-09-13 19:27

# 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 »

micwoj92 commented on 2020-09-08 01:25

It is because bitbucket no longer hosts mercurial repositories

sanerb commented on 2020-04-03 18:19

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

@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

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

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

Please add gcc49 as a dependency.

sanerb commented on 2016-09-13 19:27

# 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!

sanerb commented on 2016-09-13 11:14

actually, i'm going to create a totally different package for this- zandronum-hg
they've changed a fair bit of stuff and i'm not comfortable using a random build, so let's build it ourselves. :)

sanerb commented on 2016-09-05 20:22

@jlanzobr-

the 160814-2010 release doesn't have a linux archive/build yet, just windows. http://zandronum.com/download#betas

EDIT: there's a tarball hosted right on the build server, apparently, at https://csnxs.uk/archive/id/doom/sourceports/zandronum/builds/linux/betas/zandronum-linux-x86_64-3.0-alpha-160814-2010.tar.gz but not on the site yet. However, it's not linked to on the "official" beta section yet so I presume it's not part of the official dev channel (yet)- I'll check in a couple days to see if it's available on the main site. If not, I'll try to unpack that testing build and see if it works.

sanerb commented on 2016-06-26 06:22

Please note the following additions:

# 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.

Thanks!