Latest upstream release: 0.9.19 Current version in Fedora Rawhide: 0.9.18 URL: http://download.gna.org/hedgewars/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
I am starting to work on this. If anyone else is looking at this be aware that they did a source archive rebuild with a lower version number that isn't pointed to anywhere, but is in the download files directory. This rebuild includes some new commits from the source repository.
Latest upstream release: 0.9.19.1 Current version in Fedora Rawhide: 0.9.18 URL: http://download.gna.org/hedgewars/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
A new 0.9.19.1 was spun. So that will probably be the one we want for the update.
No Bruno, they fixed so much in 0.9.19 branch after the .1 release, there is a .2 they gave directly to me, they didn't upload yet it is better to grab it from here https://code.google.com/p/hedgewars/source/list?name=0.9.19 and make package it, or to grab from my orig.tar.gz https://code.launchpad.net/~costamagnagianfranco/+archive/costamagnagianfranco-ppa/+files/hedgewars_0.9.19.2.orig.tar.bz2 my is two commits behind of the 0.9.19 branch, I didn't repackage it because of two really little changes in the .19 branch
Thanks for the heads up. I'll just wait for the .2 release to be available before I actually put out a new package.
I haven't seen 0.9.19.2 source show up yet on the official download page nor have I seen a later tag. It's been a week since the respin of 0.9.19.1, so I am planning to use 0.9.19.1 as I get time to work on packaging it. I can do an update later when there is a new release.
They gave .3 to me just with dropbox https://dl.dropboxusercontent.com/u/24468/hedgewars-src-0.9.19.3.tar.bz2 anyway ju can just build the archive yourself with this branch https://code.google.com/p/hedgewars/source/list?name=0.9.19 and calling cpackvars.cmake
They still haven't tagged a 0.9.19.3. The only tag is 0.9.19-release. I can still use the latest release to work out changes to the lua patch and by the time I get that straightened out there may be a new official release.
I don't think they will tag any 0.9.19.3, you just need to grab the latest .19 branch
Latest upstream release: 0.9.19.3 Current version/release in Fedora Rawhide: 0.9.18-7.fc20 URL: http://download.gna.org/hedgewars/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
0.9.19 requires physfs 2.1.0 and we only have 2.0.3. So this is going to wait until that physfs gets updated. This also will make it harder to backport 0.9.19 to released versions of Fedora.
And even better news, physfs 2.1.0 hasn't actually been released yet.
Sorry Bruno, why don't just use the embedded library inside hedgewars?
Because bundled libraries are prohibited in Fedora. (Though usually they are old versions, not unreleased ones.) I'm not going to push the physfs maintainer to push out a development release, especially to older releases of Fedora. I am also not to sure that I have a good argument for a bundling exception from FESCO. When I get time I might try to figure out how hard it would be to get it to work around things to work with 2.0.3. But what little time I have left this weekend is going to be trying to get 0.9.18 to build again with the new version of ghc.
Latest upstream release: 0.9.20 Current version/release in Fedora Rawhide: 0.9.18-11.fc21 URL: http://download.gna.org/hedgewars/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 0.9.20.3 Current version/release in Fedora Rawhide: 0.9.18-11.fc21 URL: http://download.gna.org/hedgewars/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 0.9.20.4 Current version/release in Fedora Rawhide: 0.9.18-11.fc21 URL: http://download.gna.org/hedgewars/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 0.9.20.5 Current version/release in Fedora Rawhide: 0.9.18-11.fc21 URL: http://download.gna.org/hedgewars/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Hello, I hope you can solve this frustrating problem. I think that they would not release new updates with packages under development.
I think using 2.0.3 and patching it can be really easy, since hedgewars uses only three function of the development libray (not available in 2.0.3) http://code.google.com/p/hedgewars/issues/detail?id=765&thanks=765&ts=1389527977 can you guys please work on it?
It's not clear what we want to do here. It might be worth encouraging the physfs project to make a real 2.1 release. (Even then there could be significant work getting the 2.1 into Fedora if it isn't backwards compatible.) We could look into packaging both the 2.0.3 and 2.1 (prelease) versions. This again would be significant work, but it could be done. The Fedora physfs maintainer would be a good person to discuss the previous two options with. We could look at what is new in 2.1 that is being used in Hedgewars (which you have done some research on) and try to do a minimal patch to include just those extra functions and use 2.0.3 for the rest. We could wait until 2.1 is available in Fedora or until hedgewars provides a conditional build that works with 2.0.3. (This is what I have been doing.) We could ask for permission to bundle 2.1. (I don't like this. I think we'd be better off making 2.0.3 and 2.1 available at the same time for all of Fedora.) I don't think I personally will have time to try to do a wrapper (or recreate the 2.1 functions) needed soon. There is other Fedora stuff that is higher priority for me. But if someone else did most of the leg work on this I could help get those changes incorporated into Fedora in a timely manner.
Hi Bruno, the wrapper is here! http://code.google.com/p/hedgewars/source/detail?r=3858d99476f5 Can you please help in testing it? I really would like to upload this on debian too
NOTE: this version doesn't work with symlinks, in debian we symlink fonts and this doesn't work, please follow up on irc or on the issues
In the last few commits they added a new CMake Variable, now you can use system fonts, saving a bunch of space when building hedgewars this commit is a good start, but the previous and next gives you a complete patch. https://code.google.com/p/hedgewars/source/detail?r=8455993a7a1b51b38a84693817966180c0c2fded
You can cherry pick those two patches http://anonscm.debian.org/gitweb/?p=collab-maint/hedgewars.git;a=blob;f=debian/patches/using_system_fonts.patch;h=d218444e2530a7a3629752277309932c4429cacc;hb=36da3f112540150b1e3c451615db91fccb9bfb9a http://anonscm.debian.org/gitweb/?p=collab-maint/hedgewars.git;a=blob;f=debian/patches/using_system_physfs.patch;h=de0763339abc319601c86d24665244e28a4f7667;hb=36da3f112540150b1e3c451615db91fccb9bfb9a and you will be able to use system physfs and system fonts with something like this -DCMAKE_INSTALL_PREFIX=/usr/lib/hedgewars -DDATA_INSTALL_DIR=/usr/share/games/hedgewars -DCMAKE_BUILD_TYPE=RELEASE -DPHYSFS_SYSTEM=ON -DFONTS_DIRS='/usr/share/fonts/truetype/wqy;/usr/share/fonts/truetype/dejavu'
ping!
Pong. It's on my list, but I still haven't carved out a block of time to work on this yet.
Unfortunately I really would like to help, but I don't know how to contribute, moreover I'm not good at fedora packaging scripts... :(
You have helped. Without digging up the stuff for using the old phyfs library, I wouldn't even be thinking of upgrading hedgewars right now. The information just didn't get to me at a good time. But the next significant (more than a couple hours) fedora packaging work I do will be hedgewars.
any news on this?
(In reply to Ignacio Casal Quinteiro (nacho) from comment #30) > any news on this? The last time I asked, the assigned replied me that developers are working on getting a newer hedgewars to Fedora.
I grabbed the latest source and started doing some of the work a few weeks ago, but have had distractions the last few weekends. I need to fix up some old patches and test the new ones yet. So it's several hours of concentrated work assuming nothing major crops up. I should start making progress again soon.
What is the status of the package? I am trying to play the game with some friends for about 3 month, and have to boot Windows, to play hedgewars, because 0.9.18 is not compatible with 0.9.20-5.
Hello. Is there any news?
ping
Hi guys! I've had success in building from sources. We won a Christmas gift from hedgewars developers, the version 0.9.21 (http://hedgewars.org/node/5897). The steps are: 1. Download the sources. I prefer download a torrent (and share it): http://hedgewars.org/download/hedgewars-src-0.9.21.tar.bz2.torrent 2. Hence, to build we need to install some dependencies: # yum install make automake gcc gcc-c++ mingw64-qt-qmake qt-devel SDL-devel SDL_net-devel SDL_mixer-devel SDL_image-devel SDL_ttf-devel fpc lua-devel physfs-devel libpng-devel ffmpeg-devel freeglut-devel 3. With the tarball downloaded and copyed in /usr/local/src/ was enough unpack it: # tar -jxvf hedgewars-src-0.9.21.tar.bz2 4. Sign in directory: # cd hedgewars-src-0.9.21/ 5. Use cmake: # cmake -DNOSERVER=1 If errors occur, use the following command (tip from user "sheepluva" at channel #hedgewars.org), 'cause fedora only has an unsupported version of lua: # cmake -DNOSERVER=1 -DLUA_SYSTEM=0 6. Compile, install and enjoy this great game! # make install Happy 2015 to all !!!
I'm going to have time to tak another look at this over the next few days.
*** Bug 1177944 has been marked as a duplicate of this bug. ***
It looks like I'll probably be able to get 0.9.21 to build. The libphysfs issue seems to be fixed. Working around not having bytestring-show didn't take much tweaking. I'm up to seeing if I can get the lua 5.2 patch working again. The compile options still have to be fixed up but that is pretty minor. There are also a couple of new files that get installed. And of course it needs to be tested to make sure it works in addition to building.
We have a lua 5.1 compatibility library that looks like it will save me from having to redo the lua 5.2 patch. Assuming that really works (the server does build), things are looking pretty good for getting 0.9.21 out this weekend.
I have a rawhide build now. arm was excluded because it didn't build there. The game server seems to work. The game itself can't start a game on the one machine I have tested it on. I am not sure if this is video card related or some problem with the build.
Hi Bruno, I had two different build issues on arm, the patches are there https://sources.debian.net/src/hedgewars/0.9.21-3/debian/patches/0001-Fix-arm-build-failures.patch/ https://sources.debian.net/src/hedgewars/0.9.21-3/debian/patches/0001-Use-ghc-return-value-instead-of-looking-for-the-stde.patch/ (the second is because ghc writes on stderr when different llvm is detected)
Thanks. The first one looks like what I am seeing now. I'll look at including the second as well as I will probably hit it too. I'll note this in the arm failure bug. My higher priority right now is figuring out why I am getting an exit code 217 when trying to play a game. I suspect lua is fubared because there is some weirdness in lua-compat-devel. I want to try to confirm that.
Hi Bruno, the second patch is "debian/arm" specific, because ghc was built with an llvm version, and that version got upgraded without a rebuild. However the patch is good and already merged upstream. For the lua stuff I don't really know, are you in contact with upstream developers? they might have some hints. https://github.com/hedgewars/hw/pull/27 https://github.com/hedgewars/hw/pull/26 cheers, G.
It looks like there might have been a lua problem with mixing 5.1 and 5.2. The check for include path didn't have lua-5.1 as a possible suffix. I'll be testing this shortly.
I don't think lua is the cause of the issue I am seeing now, though I think I have fixed a potential problem there. I am seeing: Object::disconnect: Unexpected null parameter QCoreApplication::postEvent: Unexpected null receiver everytime I start a game in the terminal window while still getting the exit code 217 error message in hedgewars.
I tested this on f21 with a scratch build and had the same issue, though the exit code was 1 instead of 217. I'll see if I can test this on f20.
Created attachment 976175 [details] Debugging output It looks like the problem is likely physfs blocking following the symbolic links for fonts. (Hedgewars normally includes its own fonts, but in Fedora we replace the copies with links to the fonts provided by font packages.)
I confirmed that the symlinked font files are interacting badly with physfs. Placing a copy of the fonts where they had been replaced by symlinks, gets things to work. Fixing this shouldn't be too bad.
I have hedgewars building and working locally and have fired off another rawhide build that should work. I'll fix the arm stuff soon and after that I build copies for f21 and f20 since people need the up to date version to play with most other people.
I wasn't aware of your symlink of fonts. In debian I fixed already this issue, can you please follow my path or describe yours? Since I got most of the patches upstream my path can be the "best" one :) this is the configure script # our debian dejavu directory changed, so I use readlink for easier backports DEJAVU_DIRECTORY := $(shell dirname `readlink -f /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Bold.ttf`) # this gets hedgewars working where there is no fpc available (e.g. arm64), needs clang and glew, EXPERIMENTAL! ifeq ($(shell dpkg-query --status fpc |grep -o Package), Package) BUILD_ENGINE_C := NO else BUILD_ENGINE_C := YES endif HEDGEWARS_OPTIONS= \ -DCMAKE_INSTALL_PREFIX=/usr/lib/hedgewars \ -DDATA_INSTALL_DIR=/usr/share/games/hedgewars \ -DCMAKE_BUILD_TYPE=RELEASE -DPHYSFS_SYSTEM=ON \ -DFONTS_DIRS='/usr/share/fonts/truetype/wqy;$(DEJAVU_DIRECTORY)' \ -DNOVERSIONINFOUPDATE=1 \ -DBUILD_ENGINE_C=$(BUILD_ENGINE_C) to get it build on arm64 (if you don't have fpc) you might need to disable fstack-protector and to cherry-pick the font link lua patch. https://sources.debian.net/src/hedgewars/0.9.21-3/debian/patches/disable-fstack-protector.patch/ https://sources.debian.net/src/hedgewars/0.9.21-3/debian/patches/0001-Fix-segfault-when-BUILD_ENGINE_C-ON-and-FONTS_DIR-is.patch/
BTW why do you remove fonts? they shouldn't be installed if you pass the correct FONTS_DIRS, because of the code if (MISSINGFONTFILES) install(FILES ${MISSINGFONTFILES} DESTINATION ${SHAREPATH}Data/Fonts) endif() do you have some missing fonts? so you shouldn't remove them, otherwise it will likely segfault...
oh another nitpick https://github.com/hedgewars/hw/blob/master/share/hedgewars/Data/misc/hedgewars.desktop https://github.com/hedgewars/hw/blob/master/share/hedgewars.appdata.xml they are shipped in the source tree, can you please take from there instead of shipping your own files? they seems to be a little outdated, and something is even wrong :) e.g. "<url type="homepage">http://http://hedgewars.org/</url>"
I remove fonts as a safe guard. FONT_DIRS works correctly, so the removes do nothing. Probably what I should do is put in code that will make the build fail if any fonts show up rather than to try and remove two that I know about. (The danger is new ones getting added without me noticing.) Yes, I can look at getting appdata from upstream. Do you have the ability to test arm packages? Otherwise I can only see if things build or not. I am seeing a problem with the volume adjustment not working. If that is still happening when the other stuff gets fixed, I'll file a Fedora bug for it for tracking.
Oh, and thanks for doing the review. It is easy to miss things and having a second pair of eyes is helpful.
ok wonderful, I hope we can sync hedgewars more closely from debian and fedora, just to don't spare time anymore ;) >I remove fonts as a safe guard. FONT_DIRS works correctly, so the removes do nothing. Probably what I should do is put in code that will make the build fail if any fonts show up rather than to try and remove two that I know about. (The danger is new ones getting added without me noticing.) seems legit :) >Do you have the ability to test arm packages? Otherwise I can only see if things build or not. I remember I tested on rpi a while ago... it was working correctly, and I didn't get any arm bug reports so far... >I am seeing a problem with the volume adjustment not working. If that is still happening when the other stuff gets fixed, I'll file a Fedora bug for it for tracking. something new for me! quick look to patches: hedgewars-lua-search.patch --> now upstream'd hedgewars-multilib.patch --> why do you need it? hedgewars-no-bytestring.patch --> why do you still need it? if you don't plan to add bytestring to fedora I might consider asking upstream to merge this one... spec file: ExcludeArch: ppc64 s390 s390x %{arm} will you enable arm again then? >%ifarch %{arm} >%cmake -DMINIMAL_FLAGS=1 -DNOVIDEOREC=1 -DFONTS_DIRS="/usr/share/fonts/wqy-zenhei;/usr/share/fonts/dejavu" . >%else >%cmake -DMINIMAL_FLAGS=1 -DNOVIDEOREC=1 -DGHFLAGS=-dynamic -DFONTS_DIRS="/usr/share/fonts/wqy-zenhei;/usr/share/fonts/dejavu" . >%endif I don't get the MINIMAL_FLAGS and GHCFLAGS dynamic one... >%{_libdir}/libphyslayer.so what does this mean?
The multilib patch is because on x86_64 /usr/lib is for 32 bit libraries and /usr/lib64 is for 64 bit libraries. physfslayer needs to go into /usr/lib64 . $LIB_SUFFIX will either be empty or 64 depending on the arch. I plan to re-enable arm shortly. Probably this week, maybe tonight. %{_libdir}/libphyslayer.so just declares a file to be packaged. As far as I can tell physfslayer is a hedgewars specific helper library for physfs. The correct bytestring package may eventually get added to Fedora. I don't think it is blocked, just that no one has spent time on it yet. So I don't think we want to upstream that one yet. The MINIMAL_FLAGS cuts back on the compilation flags set by hedgewars so that they don't override ones standard for Fedora without a good reason. The -dynamic option is for dynamic linking of ghc modules. I wouldn't upstream that. -dynamic isn't real mainstream for ghc yet (or at least the last time I checked).
>The multilib patch is because on x86_64 /usr/lib is for 32 bit libraries and >/usr/lib64 is for 64 bit libraries. physfslayer needs to go into /usr/lib64 . >$LIB_SUFFIX will either be empty or 64 depending on the arch. this is different in debian... I mean, if that library is meant to be used only by hedgewars it should be in /usr/lib/hedgewars/lib ls /usr/lib/hedgewars/lib/lib* /usr/lib/hedgewars/lib/libavwrapper.so /usr/lib/hedgewars/lib/libphyslayer.so ldd /usr/lib/hedgewars/bin/hedgewars libphyslayer.so => /usr/lib/hedgewars/bin/../lib/libphyslayer.so (0x00007fca29435000) so no other programs gets wrongly linked against it :) but "de gustibus" ;) >%{_libdir}/libphyslayer.so just declares a file to be packaged. As far as I >can tell physfslayer is a hedgewars specific helper library for physfs. yes I noticed it after posting, I was confused because we also have avwrapper (BTW can't still it be packaged?) >The correct bytestring package may eventually get added to Fedora. I don't >think it is blocked, just that no one has spent time on it yet. So I don't >think we want to upstream that one yet. ack thanks >The MINIMAL_FLAGS cuts back on the compilation flags set by hedgewars so that >they don't override ones standard for Fedora without a good reason. I don't think they override anything... at least I don't see in my logs https://buildd.debian.org/status/fetch.php?pkg=hedgewars&arch=amd64&ver=0.9.21-3&stamp=1419958917 >The -dynamic option is for dynamic linking of ghc modules. I wouldn't upstream >that. -dynamic isn't real mainstream for ghc yet (or at least the last time I >checked). ok, so I won't take that one for debian :) thanks!
http://download.gna.org/hedgewars/hedgewars-src-0.9.21.1.tar.bz2 Just FYI, there is a new tarball with the arm/ghc/lib fixes :)
Latest upstream release: 0.9.21.1 Current version/release in Fedora Rawhide: 0.9.21-3.fc22 URL: http://download.gna.org/hedgewars/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Soon this service will be implemented by a new system: https://release-monitoring.org/ It will require to manage monitored projects via a new web interface. Please make yourself familiar with the new system to ease the transition.
I have a build of 0.9.21.1 for rawhide now. It is supposed to take care of everything I was planning to address at this time. I need to do some testing tomorrow. If things look good, I'll do f21 and f20 builds.
hedgewars-0.9.21.1-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/hedgewars-0.9.21.1-1.fc21
hedgewars-0.9.21.1-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/hedgewars-0.9.21.1-1.fc20
Package hedgewars-0.9.21.1-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing hedgewars-0.9.21.1-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-0558/hedgewars-0.9.21.1-1.fc21 then log in and leave karma (feedback).
hedgewars-0.9.21.1-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
hedgewars-0.9.21.1-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
bruno's hedgewars-0.9.21.1-3.fc23 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=612166