Updating from 3.7.16 to 3.7.18 in linux

Technical Support & Bugs
1

Hello,

I was able to get the Vassal version 3.16 working on linux thanks to help from Christian’s replies. It’s been working good, but I went to try to put the 3.18 version on and it seems like I got the unpacked parts to the right directory, but the integration command isn’t doing anything there.

Or.. am I just missing an easier way to update the version in linux?

Thanks,

Forest

2

In order to help you, we need more details. What are did you do? How did it fail? What error messages were there?

(BTW, the correct version numbers are 3.7.16 and 3.7.18. “3.16” and “3.17” don’t refer to any releases we’ve made to date.)

3

Okay, well then to correct - with help in another forum post here, I was able to get Vassal version 3.7.16 on my linux system. It is working well, but with recent new versions coming out I was trying to see if I could get version 3.7.18 on. I put the download in the same directory as the 3.7.16 is in, unpacked it there - looks like similar folders, files, etc in it. Tried the integration command (from the forum post that explains as I did for first putting the 3.7.16 version on) in that directory - the one with 3.7.18 - and the command didn’t do anything as far as I can tell. So I’m not sure where to go from here. Like I say the 3.7.16 is working fine for games I’m playing now and probably would for a while, just trying to stay updated here.

My linux version is Pop-OS. Computer is 64-bit laptop. Just let me know what other info you need.

Thanks!

Forest

4

What we need to know is what the exact steps you took were. What file did you download? What were the commands you ran? What were the results?

5

Okay:

  • downloaded 3.7.18 version for linux
  • put that unpacked download in my ‘vassal’ directory which is where the folder/directory for currently used version 3.7.16 is at
  • unpacked the 3.7.18 version there - so now there are two folders in my vassal directory, one for each version
  • changed directory to the 3.7.18 one and tried the integration command from the post here on that - I think it is /integration.sh or something like that, but no results from that, or at least when I start vassal again it’s still showing 3.7.16.

So obviously I did something wrong here but not sure what or at what point.

Thanks,

Forest

6

Where is this?

7

Here:

8

Ok. That’s not an approach I’ve worked through myself, so I can’t comment on it.

What I would do is try running the VASSAL.sh script which came with 3.7.18 from the command line. What happens when you do that?

9

That did work from the command line to start up vassal and open a mod in version 3.7.18. But then after that when I tried it from my desktop Vassal icon and also the icon for the mod of a game I’m currently playing, it started up in 3.7.16 version again. How can I get it to start from the newer version there, or put a new shortcut on my desktop? I didn’t see a way to do that.

Thanks,

Forest

10

OK, let me see if I got your situation correct. You have the following directories

~/vassal -+- VASSAL-3.7.16
          |  + ...
          |  +- VASSAL.sh
          |  `- integration.sh
          +- VASSAL-3.7.18
             + ...
             +- VASSAL.sh
             `- integration.sh

When you execute VASSAL through desktop menus or by double-clicking a .vmod or similar, you will execute ~/vassal/VASSAL-3.7.16/VASSAL.sh - not ~/vassal/VASSAL-3.7.18/VASSAL.sh as intended.

Perhaps you could say how you did the How to Integrate VASSAL into the Linux Desktop procedure - for all users (option -s) or for a single user. Assuming you did if for a single user, then look at the content of

~/.local/share/applications/application-x-vassal.desktop

It most likely has lines like

Exec=/home/some/user/vassal/VASSAL-3.7.16/VASSAL.sh

To fix that, go into your VASSAL-3.7.16 directory and execute integration.sh with the -r option

$ cd ~/vassal/VASSAL-3.7.16
$ ./integration.sh -r

Now to point to version 3.7.18, change directory to your VASSAL-3.7.18 directory and execute integration.sh with appropriate options

$ cd ~/vassal/VASSAL-3.7.18
$ ./integration.sh

If you had over-written your 3.7.16 directory fully with 3.7.18, then you wouldn’t need to do the integration step again. Or if you had made a symbolic link to your current installation, and specified that as the installation directory for the integration.sh script, you wouldn’t need to redo it again. E.g.,

$ cd vassal
$ tar -xjf ../Downloads/VASSAL-linux-3.7.16.tar.bz2 
$ rm -f current
$ ln -s VASSAL-3.7.16 current 
$ ./integration.sh -v `pwd`/current  # Only needed once

and on update

$ cd vassal 
$ tar -xjf ../Downloads/VASSAL-linux-3.7.18.tar.bz2 
$ rm -f current
$ ln -s VASSAL-3.7.18 current

As Pop!-OS is a derivative of Debian, you will in the not too distant future, be able to download a Debian package and install VASSAL through that. That will provide seamless installation and integration. You can try a preview vassal_3.7.19-SNAPSHOT-e8de2b8-1_all.deb. After downloading, simply do

$ sudo apt install ~/Downloads/vassal_3.7.19-SNAPSHOT-e8de2b8-1_all.deb

(make sure you run integration.sh -r first).

Yours,
Christian

Yours,
Christian

11

Okay, I’m an idiot.. so yes you had at least as I described correct. But then since you lined it up there with the scripts in both directories, I went and checked. The integration script was in the 3.7.16 folder but not in the 3.7.18 one.. sigh.. So I just copied it over there, ran the integration script in 3.7.18 directory, and now everything opens to version 3.7.18!

I did not see where I could write over files but maybe just didn’t catch that..

Looking forward to the 3.7.19!

Thanks much for you guys’ responsiveness and help, and as always for this software to play our games!

Forest