Package Details: 0ad-data-git 1:A26.r1310.g899a956de4-1

Git Clone URL: https://aur.archlinux.org/0ad-git.git (read-only, click to copy)
Package Base: 0ad-git
Description: Data package for 0ad built from git development version.
Upstream URL: http://play0ad.com/
Licenses: CCPL, GPL-2.0-or-later
Conflicts: 0ad-data
Provides: 0ad-data
Submitter: fusion809
Maintainer: tuxayo (micwoj92)
Last Packager: micwoj92
Votes: 7
Popularity: 0.000148
First Submitted: 2016-09-09 11:31 (UTC)
Last Updated: 2024-04-09 21:30 (UTC)

Required by (2)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4

a36233 commented on 2018-05-17 15:47 (UTC)

==== Building scriptinterface (release) ==== precompiled.h In file included from ../../../source/lib/sysdep/stl.h:32, from ../../../source/lib/precompiled.h:68, from ../../../source/pch/scriptinterface/precompiled.h:19: /usr/include/c++/8.1.0/cstdlib:75:15: fatal error: stdlib.h: No such file or directory #include_next <stdlib.h> ^~~~~~~~~~ compilation terminated. make[1]: [scriptinterface.make:121: obj/scriptinterface_Release/precompiled.h.gch] Error 1 make: [Makefile:105: scriptinterface] Error 2</stdlib.h>

JeromeS commented on 2017-05-20 04:24 (UTC)

Build fails since the update of icu, with an error in Fcollada. I get plenty of error like this message: /usr/include/unicode/umachine.h:347:13: error: « char16_t » is not a type typedef char16_t UChar; Any idea what I'm doing wrong?

jamincollins commented on 2017-02-05 22:49 (UTC)

@fusion809, if you don't have the tools to properly maintain the package(s) please consider orphaning the package or recruiting a co-maintainer that does have the tools.

fusion809 commented on 2017-02-05 21:52 (UTC)

@jamincollins I would if I still had an Arch Linux system to do this on. I can still do routine maintenance (like bumping package versions, making adjustments to the PKGBUILD, etc.) on my AUR packages but I can't do what you're mentioning as I don't have the tools to build.

jamincollins commented on 2017-02-05 21:37 (UTC)

This package fails to successfully build in a clean chroot. ==8<========================================================================== ... ==> Validating source files with md5sums... 0ad ... Skipped ==> ERROR: Cannot find the git package needed to handle git sources. ==> ERROR: An unknown error has occurred. Exiting... ERROR: Build failed: exit status 1 ==8<========================================================================== The following changes correct this: ==8<========================================================================== diff --git a/PKGBUILD b/PKGBUILD index f4af7da..fe169d4 100644 --- a/PKGBUILD +++ b/PKGBUILD @@ -13,7 +13,7 @@ license=('GPL2' 'CCPL') depends=('binutils' 'boost-libs' 'curl' 'enet' 'libogg' 'libpng' 'libvorbis' 'libxml2' 'openal' 'sdl2' 'wxgtk' 'zlib' 'libgl' '0ad-data' 'glu' 'gloox' 'miniupnpc' 'icu' 'nspr') -makedepends=('boost' 'cmake' 'mesa' 'zip' 'python2' 'libsm') +makedepends=('boost' 'cmake' 'mesa' 'zip' 'python2' 'libsm' 'git') source=("git+https://github.com/0ad/0ad.git") md5sums=('SKIP') ==8<========================================================================== Please consider testing new package versions by building them in a clean chroot[1], with something like the following: ==8<========================================================================== #!/bin/bash BUILD_CHROOT=~/.local/build-chroot test -d ${BUILD_CHROOT} || \ mkdir -p ${BUILD_CHROOT} test -d ${BUILD_CHROOT}/root && \ arch-nspawn ${BUILD_CHROOT}/root pacman -Syu || \ mkarchroot ${BUILD_CHROOT}/root base-devel makechrootpkg -c -n -T -u -r ${BUILD_CHROOT} -- --cleanbuild ==8<========================================================================== [1] - https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot

fusion809 commented on 2016-11-09 07:42 (UTC)

@cRaZy-bisCuiT git packages shouldn't be flagged as out of date because they are automatically updated to the latest version whenever you build them!

fusion809 commented on 2016-10-21 18:04 (UTC)

@Imat, never heard of it. Guessin' it clones the repo with only the top-level contents? If it omits any part of the repo's contents my guess is no. Most git repos try to only include vital components, so if you strip anything from them it will likely lead to problems.

lmat commented on 2016-10-21 17:59 (UTC)

Is it possible to use a shallow clone? (git clone --depth 1; or whatever)

« First ‹ Previous 1 2 3 4