3.1 release OSDN commit hash tag mismatch?

killall -9

Moderator: Developers

Post Reply
string
New User
Posts: 2
Joined: Thu Jan 20, 2022 11:40 pm

3.1 release OSDN commit hash tag mismatch?

#1

Post by string » Fri Jan 21, 2022 12:19 am

When compiling the zandronum 3.1 server release "ZA_3.1 4178904d7698" tag from osdn

clients complain that...
Server uses: 3.1-R-300101-0000
You use: 3.1-R211211-2135

Is there a way or a proper commit hash I can use to access the proper source code for compiling a 3.1 release binary?

User avatar
Sean
IRC Operator
Posts: 941
Joined: Thu Jan 16, 2014 9:09 pm
Location: United Kingdom
Contact:

Re: 3.1 release OSDN commit hash tag mismatch?

#2

Post by Sean » Fri Jan 21, 2022 5:19 am

Make sure you cloned using Mercurial and didn't use the zip/tar archives.

Code: Select all

hg clone -r ZA_3.1 https://hg.osdn.net/view/zandronum/zandronum-stable
<capodecima> i dont say any more word without my loyer jenova

string
New User
Posts: 2
Joined: Thu Jan 20, 2022 11:40 pm

Re: 3.1 release OSDN commit hash tag mismatch?

#3

Post by string » Sun Jan 23, 2022 8:21 am

Gracias. Perfecto. I suppose my mercurial skills weren't up to par.

Post Reply