Page 1 of 1

[SOLVED] DDNet Client 10.0 is still recognized as 9.3.1

Posted: Thu May 05, 2016 12:22 am
by rafaelff
I maintain a DDNet Client package in Arch User Repository (a.k.a. AUR), for archlinux distribution, and I'm having one difficult in the upgrade process of 9.3.1 to 10.0.1.

Firstly, I do not use the "Update" feature in my package. As can be seen in the package's installation script, a.k.a. PKGBUILD, I have been doing only installation of files in the proper place.

Now, for version 10.0, tested my package locally and the NEWS is always displayed (like, "hey, there is a new version") and the bottom of the Server Browse screen shows "0.6.2 9.3.1".

My package installation worked just fine, but looks like the update process of 10.0.1 is slightely different -- In Windows, I notice it updates twice. Probably some change in the user's personal information or any other thing that I'm not aware of.

So, what is different in the update procedure from 9.3.1 to 10.0.1, and what does it takes for me to make my package's version be recognized correctly as version 10.0.1?

Re: DDNet Client 10.0 is still recognized as 9.3.1

Posted: Thu May 05, 2016 1:29 am
by deen
I appreciate the AUR package and use it myself on my laptop. (Installing all the skins can cause problems for people with low memory btw)

Some things that changed that might be relevant for you:
  • SDL2 instead of SDL1.2
  • tar.xz instead of tar.gz
  • Updater uses update2.ddnet.org instead of update.ddnet.org
Does it work with your PKGBUILD instructions manually? I guess I can take a closer look at it.

Edit: Since DDNet is open source, wouldn't it be more appropriate to compile the source code with the PKGBUILD? Then you don't get our bundled library versions and can use the arch ones instead (libcurl, opus, ogg, ...)

Edit2: I just took your PKGBUILD, changed version to 10.0.1 and it installed correctly. Shows the correct version as well.

Re: DDNet Client 10.0 is still recognized as 9.3.1

Posted: Fri May 06, 2016 1:18 am
by rafaelff
Thanks for the reply. Well, it indeed worked. Probably some bug between keyboard and chair...

Initially, I set this PKGBUILD to build package from binary because I was unsure if it would be harder to maintain otherwise (e.g. with pcsx2-git I used to need to tweak a lot of stuff). But now that you mentioned, I changed to the PKGBUILD accordinly.

For your information, in this new version I move away skins to teeworlds-ddnet-skins and also created teeworlds-ddnet-maps-git to allow a lot of features provided in ddnet-maps git repository.

EDIT: marked thread as SOLVED.

Re: [SOLVED] DDNet Client 10.0 is still recognized as 9.3.1

Posted: Fri May 06, 2016 1:39 am
by deen
Looks great. But it's still using the bundled libraries instead of system ones: zlib, curl, opusfile, opus, ogg. See the configuration step of "bam release"

Re: [SOLVED] DDNet Client 10.0 is still recognized as 9.3.1

Posted: Fri May 06, 2016 2:28 am
by kamillentee
Great you moved skins in a extra package, I always needed to remove it manually. And creating package for maps is a good idea too. But I still have problems with the openssl package (removed it always in PKGBUILD so far) What is the package needed for? You can simply install openssl using the official repos.

Re: [SOLVED] DDNet Client 10.0 is still recognized as 9.3.1

Posted: Fri May 06, 2016 6:00 pm
by rafaelff
Thanks guys for the feedback!
deen wrote:Looks great. But it's still using the bundled libraries instead of system ones: zlib, curl, opusfile, opus, ogg. See the configuration step of "bam release"
Really? That's weird, as I saw in the build output indications that those libs were set via pkg-config. See the output.
Not sure where to look for the configuration step of Release. I took a look in bam.lua, but I don't "speak" Lua very much. Can you please point it for me?
kamillentee wrote:Great you moved skins in a extra package, I always needed to remove it manually. And creating package for maps is a good idea too. But I still have problems with the openssl package (removed it always in PKGBUILD so far) What is the package needed for? You can simply install openssl using the official repos.
If I remember correctly, I added openssl098 because DDNet implemented a communication with SSL (don't remember specifics or when), and namcap showed dependency to openssl098- that is for building package with the binary file.
But now that you brought up this subject, I notice that building from source code just requires adding opusfile and curl, without needing openssl098. In matter of fact, curl depends on openssl, so no need adding openssl (or openssl098, of course). PKGBUILD updated with +opusfile, +curl and -openssl098.

Re: [SOLVED] DDNet Client 10.0 is still recognized as 9.3.1

Posted: Mon May 16, 2016 1:40 pm
by deen
You can't use md5sum for the ddnet-skins btw, since the zip file is regenerated whenever a skin is added.

Re: [SOLVED] DDNet Client 10.0 is still recognized as 9.3.1

Posted: Mon May 23, 2016 4:11 pm
by rafaelff
Fixed.