Created attachment 213669 [details] Port diff Please update lugaru to 1.3 This version is based on my repository on github which is a fork of this read-only repo: https://github.com/osslugaru/lugaru. The major changes compared to the version in ports is migration to SDL2 and memory corruption fix when drawing sprites.
Build info is available at https://gitlab.com/swills/freebsd-ports/pipelines/138576075
Hi, I am the new maintainer of lugaru. I think it is preferable to keep lugaru port following the official software rather than forks. Thus I suggest you to do one of the following: - submit your patches upstream: https://gitlab.com/osslugaru/lugaru - make your fork a new stand alone software and create a new port for it. According to your description, your fork is essentially the original game improved, then I recommend following the first path. In the meantime, I plan to update the port to version 1.2 from https://gitlab.com/osslugaru/lugaru (as you know we are still tracking old version from bitbucket). If you want to give a help and submit the patch here, you're welcome.
The last commit on GitLab repository was 8 months ago. That's why I decided to switch to a fork. Also I really do not want to get an account on GitLab for just a one game ;( Maybe you can add my patches to the port itself or I can do it if you attach your new port here. The version upstream is completely broken. You can play at most one minute before it crashes. It contains a piece of code like this: vector<foo> bar; ... for (int i=0; i<bar.size(); i++) { if (condition) bar.erase (bar.begin() + i); } If this is not fixed, the game will no be playable, so my patches are super-puper-mega important;) See https://github.com/shamazmazum/lugaru/commit/09adc18d56cd87f65d9ace34369ec389f9013b02 and https://github.com/shamazmazum/lugaru/commit/9204227ad2c4587144e2281a9d752a5efc840aac
If version 1.2 is indeed broken and/or if the software is unmaintained upstream this is different indeed. I am trying to contact upstream to check if the project is still active: if it is I will point them to your patches, if it is not I will switch to your fork after having confirmed that 1.2 is indeed broken.
Thanks!
I successfully contacted the lugaru team on irc (#lugaru on freenode) and they are looking into your commits: https://gitlab.com/osslugaru/lugaru/-/issues/113 They also told me that you can use your github account on gitlab. They are working on a maitainance release (1.2.1): https://gitlab.com/osslugaru/lugaru/-/issues/112 We will make sure that 1.2.1 works on FreeBSD as well and I will update the port consistently. Thanks for your work.
My patches are sent
Oh, thanks for totally ignoring my work! Probably anyone who installs this port and runs the game is experiencing crashes now.
I see this port is based not on the master, but on some commit which fixes animation. Good, but my biggest problem was on drawing sprites. This is a backtrace of crashed lugaru built from master: (lldb) bt * thread #1, name = 'lugaru', stop reason = signal SIGSEGV * frame #0: 0x000000000024ff05 lugaru`Sprite::Draw() at Sprite.cpp:407:25 frame #1: 0x00000000002d881b lugaru`Game::DrawGLScene(side=stereoCenter) at GameDraw.cpp:545:9 frame #2: 0x000000000021fb60 lugaru`main(argc=<unavailable>, argv=<unavailable>) at main.cpp:718:21 frame #3: 0x000000000021e10f lugaru`_start(ap=<unavailable>, cleanup=<unavailable>) at crt1.c:76:7 On c7b99378439735c60f84869b05c6ebde53083667 such problem does not occur, but I don't see how it is fixed. Problems with memory can be well hidden and manifest themselves later on some irrelevant change in the code or environment. But, whatever, I do not care anymore. I also don't think you are the right person to blame, but developers of lugaru are. Maybe they will run across that bug sometimes and fix it on their own.
(In reply to shamaz.mazum from comment #9) Do not worry, your contributions have not been ignored. As I wrote earlier, I reported them upstream and developers are discussing in this issue which is still open: https://gitlab.com/osslugaru/lugaru/-/issues/113 If you want you can partecipate to the discussion and try to convince them of the validity of your work. Moreover, the developers are working to a new maintenance release and this will probably include anything that is found useful from your work. If you still happen to disagree with the developers you can fork the game as you already did, but make sure that is is clear that it is a fork. In particular do not keep calling it lugaru: this creates confusion and people cannot distinguish your fork and the original game easily. Once your fork is ready you can create a new port in the FreeBSD ports tree for it. However, as a port maintainer, I cannot change a port to track a fork if it is maintained upstream, even if it is buggy. If there is a bug it must be reported upstream and fixed upstream; if it is not fixed upstream then developers are doing bad work and someone should fork the software, but in a clear manner that do not create confusion. I hope this experience will not discourage you to contribute again to FreeBSD, lugaru or any open source project.
Thanks. At least the port is upgraded and playable ;)