Jump to content

Vincent

Community Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by Vincent

  1. Thanks for the report (y) Any indication as to why 0 A.D. is included at this moment and not either sooner or once we reach 1.0?

    2 simple reasons:

    1) I finally have some spare time now that exams are over. :D

    2) The freeze date for Debian wheezy is rapidly approaching (mid-June), and I want to clear up the backlog of stuff that I intend to package before that happens. 0 A.D. has been sitting on my packaging TODO list for months now.

    I'm somewhat surprised that Ubuntu picked up 0 A.D. so quickly (I thought Debian import freeze took place back in January?), but then again, I'm not as familiar with Ubuntu's release cycle as I am with that of Debian.

    Anyways, I just wanted to give a shoutout to ricotz for his packaging work (which I used as a base for my own set of packages) and to fabio for all his help and advice these past few weeks as I packaged 0 A.D. Thanks! :)

  2. What version of gzip do you have? ("gzip -V" should say). The .gz files are created by 7zip so maybe it's doing something unusual that certain versions of gzip don't like, or something?

    $ gzip -V
    gzip 1.3.12
    Copyright (C) 2007 Free Software Foundation, Inc.
    Copyright (C) 1993 Jean-loup Gailly.
    This is free software. You may redistribute copies of it under the terms of
    the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
    There is NO WARRANTY, to the extent permitted by law.

    Written by Jean-loup Gailly.

    It's the stock gzip that comes with Debian. Hmmm...I just did a bit of poking around and came up with Debian bug #627121 and it looks like I might not be the only one who's experiencing this problem. I have no idea what may be causing it though.

  3. Oh, I thought that the release of r09530 tarballs meant that Alpha 5 was out already...sorry about that.

    The hashsums match, but I still seem to be unable to extract the gzipped tarball. I'm also perfectly capable of extracting other gzipped tarballs without a single problem, so I'm sort of stumped at the moment. But the xz tarball works, so I don't mind all that much. ;)

  4. Congrats on releasing Alpha 5! I look forward to playing it and checking out all the new features. :)

    However, it looks like there might be a problem with the release tarballs, i.e.

    $ wget -q http://releases.wildfiregames.com/0ad-r09530-alpha-unix-build.tar.gz
    $ tar xzf 0ad-r09530-alpha-unix-build.tar.gz

    gzip: stdin: invalid compressed data--crc error
    tar: Child returned status 1
    tar: Error is not recoverable: exiting now

    The xz-compressed archive works just fine though. Is it perhaps possible to provide hashsums for the tarballs, so it'd be possible to confirm whether or not it might be a faulty download or something like that?

  5. Hi,

    (Sorry if this is in the wrong section of the forums or anything like that.)

    I've recently just heard of 0 A.D., and I was intrigued enough to want to give it a try. However, after building alpha 4 (r09049) on my 64-bit Debian GNU/Linux system and running it, I always get the following error:

    vincent@vincent-laptop:~$ 0ad
    TIMER| InitVfs: 559.22 us
    TIMER| InitScripting: 3.7298 ms
    ERROR: Error initializing FAM; hotloading will be disabled
    file.cpp(130): Function call failed: return value was -110301 (Error during IO)
    Function call failed: return value was -110301 (Error during IO)
    Location: file.cpp:130 (WaitUntilComplete)

    Call stack:

    (0x6f684d) ./pyrogenesis() [0x6f684d]
    (0x6b6fe1) ./pyrogenesis() [0x6b6fe1]
    (0x6b7e31) ./pyrogenesis() [0x6b7e31]
    (0x6b81ed) ./pyrogenesis() [0x6b81ed]
    (0x702338) ./pyrogenesis() [0x702338]
    (0x6ccc97) ./pyrogenesis() [0x6ccc97]
    (0x6cbb8b) ./pyrogenesis() [0x6cbb8b]
    (0x6c7fd9) ./pyrogenesis() [0x6c7fd9]
    (0x70af89) ./pyrogenesis() [0x70af89]
    (0x708181) ./pyrogenesis() [0x708181]
    (0x6cde84) ./pyrogenesis() [0x6cde84]
    (0x4f118d) ./pyrogenesis() [0x4f118d]
    (0x53cecf) ./pyrogenesis() [0x53cecf]
    (0x542f05) ./pyrogenesis() [0x542f05]
    (0x41374b) ./pyrogenesis() [0x41374b]
    (0x4154e3) ./pyrogenesis() [0x4154e3]

    errno = 0 (?)
    OS error = ?


    Aborted

    I've also taken a look at the 0 A.D. PPA (https://launchpad.ne...fg/+archive/0ad), but when I try to package 0 A.D. using the sources provided there, the build fails with the following error:

    # Run tests
    LD_LIBRARY_PATH=binaries/system binaries/system/test -libdir binaries/system
    ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded: ignored.
    Running 252 tests........................................................................................................WARNING: Skipping component scripts tests (can't find binaries/data/mods/public/simulation/components/tests/setup.js)
    ...............................file.cpp(130): Function call failed: return value was -110301 (Error during IO)
    Function call failed: return value was -110301 (Error during IO)
    Location: file.cpp:130 (WaitUntilComplete)

    Call stack:

    (0x7ba9ed) binaries/system/test() [0x7ba9ed]
    (0x778f81) binaries/system/test() [0x778f81]
    (0x779dd1) binaries/system/test() [0x779dd1]
    (0x77a18d) binaries/system/test() [0x77a18d]
    (0x7c1048) binaries/system/test() [0x7c1048]
    (0x790c37) binaries/system/test() [0x790c37]
    (0x78f6d1) binaries/system/test() [0x78f6d1]
    (0x7c13a7) binaries/system/test() [0x7c13a7]
    (0x794b29) binaries/system/test() [0x794b29]
    (0x620e46) binaries/system/test() [0x620e46]
    (0x5559b2) binaries/system/test() [0x5559b2]
    (0x498560) binaries/system/test() [0x498560]
    (0x418af4) binaries/system/test() [0x418af4]
    (0x422333) binaries/system/test() [0x422333]
    (0x418dfd) binaries/system/test() [0x418dfd]
    (0x2b63409c0c4d) /lib/libc.so.6(__libc_start_main+0xfd) [0x2b63409c0c4d]

    errno = 0 (?)
    OS error = ?


    Function call failed: return value was -110301 (Error during IO)
    Location: file.cpp:130 (WaitUntilComplete)

    Call stack:

    (0x7ba9ed) binaries/system/test() [0x7ba9ed]
    (0x778f81) binaries/system/test() [0x778f81]
    (0x779dd1) binaries/system/test() [0x779dd1]
    (0x77a18d) binaries/system/test() [0x77a18d]
    (0x7c1048) binaries/system/test() [0x7c1048]
    (0x790c37) binaries/system/test() [0x790c37]
    (0x78f6d1) binaries/system/test() [0x78f6d1]
    (0x7c13a7) binaries/system/test() [0x7c13a7]
    (0x794b29) binaries/system/test() [0x794b29]
    (0x620e46) binaries/system/test() [0x620e46]
    (0x5559b2) binaries/system/test() [0x5559b2]
    (0x498560) binaries/system/test() [0x498560]
    (0x418af4) binaries/system/test() [0x418af4]
    (0x422333) binaries/system/test() [0x422333]
    (0x418dfd) binaries/system/test() [0x418dfd]
    (0x2b63409c0c4d) /lib/libc.so.6(__libc_start_main+0xfd) [0x2b63409c0c4d]

    errno = 0 (?)
    OS error = ?


    (C)ontinue, (S)uppress, (B)reak, Launch (D)ebugger, or (E)xit?
    Sleeping until debugger attaches.
    Please wait.
    Debugger launch failed: No such file or directory
    Trace/breakpoint trap
    make[1]: *** [override_dh_auto_build] Error 133
    make[1]: Leaving directory `/tmp/buildd/0ad-0~r09049~alpha4'
    make: *** [binary] Error 2
    dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2

    Does anybody know why this is happening, and how I could fix this? Thanks in advance. :)

×
×
  • Create New...