Introducing: musa. The new BaNaNaS upload tool

[Eddi]

i believe the extra-part of the svn repo has not been moved yet, find by checking out svn://svn-archive.openttd.org/extra/musa

[NekoMaster]

I'm still having issues with MUSA saying "File contains no section headers" when I try to upload my 4K USA scenario, even though the scenario loads and saves just fine in OpenTTD

[orudge]

Should you be passing the path to the INI on the command line, not the SCN itself?

[NekoMaster]

Should you be passing the path to the INI on the command line, not the SCN itself?

No, MUSA sees the INI int he folder and you direct MUSA to upload the file via the command line. This is how I did it with my North AMerican Track set

This worked for uploading my track set

Code: Select all

musa.exe -u nek0master -p NOPEPASSWORD -v -c NATS_UPLOAD.ini north_american_track_set.grf

How ever this from my USA 4K ECS Folder gives me erros

Code: Select all

musa.exe -u nek0master -p NOPEPASSWORD -v -c "USA 4K - 1950 (ECS VECTORS v2.0.2) - OpenTTD v1.7.2.scn"

Btw, I've tried using a simple name like USA4KECS.SCN as well as trying to do it all from the root of my C and D drives and nothing works.

There shouldn't be anything wrong with my scenario because I already made a rather large railroad in game with the Vanilla Industries and ECS Versions of my USA 4K scenario.

[Eddi]

i'm not quite sure you should paste your hunter2 here like that...

anyway

musa.exe -u nek0master -p x -v -c NATS_UPLOAD.ini north_american_track_set.grf
musa.exe -u nek0master -p x -v -c thing missing here "USA 4K - 1950 (ECS VECTORS v2.0.2) - OpenTTD v1.7.2.scn"

spot the difference?

[NekoMaster]

i'm not quite sure you should paste your hunter2 here like that...

anyway

musa.exe -u nek0master -p x -v -c NATS_UPLOAD.ini north_american_track_set.grf
musa.exe -u nek0master -p x -v -c thing missing here "USA 4K - 1950 (ECS VECTORS v2.0.2) - OpenTTD v1.7.2.scn"

spot the difference?

Wow I'm so fking dumb, I didn't realize that I was missing that bit to tell musa what INI to use before the file upload.

---

Now I have a new problem....

MUSA apparently doesnt know what a scenario is, because trying to upload my scenario as file type = scenario gives me an error

Code: Select all

D:\USERS\MATTHEW\Dropbox\~ OpenTTD Projects ~\[SCENARIO] USA 4K>musa.exe -u nek0master -p m@1992ASDjkl123 -v -c USA-CANADA_4K_ECS_UPLOAD.INI "USA 4K - 1950 (ECS VECTORS v2.0.2) - OpenTTD v1.7.2.scn"
reading configuration file USA-CANADA_4K_ECS_UPLOAD.INI...
creating temporary tarball...
packaging name/version information...
packaging license information...
packaging type information...
the following files will be added:
  - USA 4K - 1950 (ECS VECTORS v2.0.2) - OpenTTD v1.7.2.scn
packaging text information...
packaging files... (might take a while)
unknown type "scenario"

[NekoMaster]

Ok so now I'm getting a new error when I try to upload my 4K Scenario

Code: Select all

D:\USERS\MATTHEW\Dropbox\~ OpenTTD Projects ~\[SCENARIO] USA 4K>musa.exe -u nek0master -p NOPEPASSWORD -v -c USA-CANADA_4K_ECS_UPLOAD.INI "USA4KECS.SCN"
reading configuration file USA-CANADA_4K_ECS_UPLOAD.INI...
creating temporary tarball...
packaging name/version information...
packaging license information...
packaging type information...
the following files will be added:
  - USA4KECS.SCN
packaging text information...
packaging files... (might take a while)
Traceback (most recent call last):
  File "C:\Python27\lib\site-packages\cx_Freeze\initscripts\Console.py", line 27, in <module>
  File "musa.py", line 183, in <module>
  File "musa.py", line 93, in main
  File "type.py", line 389, in package_type
  File "C:\Python27\lib\ConfigParser.py", line 576, in get
ConfigParser.NoOptionError: No option 'uniqueid' in section: 'musa'

ANy ideas guys? I really want to get this uploaded

[acs121]

It seems to say your scenario has an already occupied ID. Unless i'm wrong...

[NekoMaster]

It seems to say your scenario has an already occupied ID. Unless i'm wrong...

Well I dunno how to change taht, its not like you can "Change" the ID for a scenario

[Moriarty]

It seems to say your scenario has an already occupied ID. Unless i'm wrong...

I'd say based on that Python error that it is expecting a "uniqueid" field in your file, under a "musa" section.

[NekoMaster]

It seems to say your scenario has an already occupied ID. Unless i'm wrong...

I'd say based on that Python error that it is expecting a "uniqueid" field in your file, under a "musa" section.

There isn't anything like that in the UPLOAD.INI that i use, I just downloaded an example INI from this thread and used that to upload my NewGRF

I really wish someone who knew what they where doing could help out with this because this is getting kind of silly that we're being forced to use a new tool with little to no help from the creator(s). I mean all I want to do is upload a scenario, is that so hard to ask for?

[Gwyd]

Sorry if this has been asked before, but is there a way to update a grf, uploaded via BaNaNaS or MUSA?

[Eddi]

of course you can update a GRF, just it has to be done by the same person that made the original upload.

[NekoMaster]

Sorry if this has been asked before, but is there a way to update a grf, uploaded via BaNaNaS or MUSA?

Yeah, you just update the INI file for your GRF and give the upload a new version number and upload that, since your project is already on Bananas the server will apply any futher uploads to your project as an update.

[NekoMaster]

I'm glad BaNaNa's is back up because this is a stupid system...

Code: Select all

D:\USERS\MATTHEW\Dropbox\~ OpenTTD Projects ~\[SCENARIO] USA 4K>musa.exe -u nek0master -p WhosPasswordCouldThisBe? -v -c USA-CANADA_4K_ECS_UPLOAD.INI usa4kecs.scn
reading configuration file USA-CANADA_4K_ECS_UPLOAD.INI...
creating temporary tarball...
packaging name/version information...
packaging license information...
packaging type information...
the following files will be added:
  - usa4kecs.scn
packaging text information...
packaging files... (might take a while)
validating files locally...
validating misc data
validating license...
validating text
validating type...
temporary tarball validated...
are you one of the authors of this content, if so answer 'yes I am': yes I am
validating metadata at server...
error: heightmaps and scenarios must be initially uploaded via bananas web manager to obtain a uniqueid
an error occurred and the content is not uploaded

D:\USERS\MATTHEW\Dropbox\~ OpenTTD Projects ~\[SCENARIO] USA 4K>pause
Press any key to continue . . .

even though I put in a line for "uniqueid" that still doesnt work because MUSA expects people to upload scenarios and heightmaps via Banana's which at the time of creating that scenario and my issues, nobody was unable to upload files via the web manager.

[Zuu]

Late to the game and everything, but for the record the Beginner Tutorial scenario is uploaded using musa. For this project it was useful to use musa because it has several content packages that need to have dependencies set up and updated on each version update upload.

But musa is a CLI tool and initial configuration is a bit more tedious than point and click. I ended up improving musa that time when I used it but after all being setup continues use is all automated.

[NekoMaster]

Late to the game and everything, but for the record the Beginner Tutorial scenario is uploaded using musa. For this project it was useful to use musa because it has several content packages that need to have dependencies set up and updated on each version update upload.

But musa is a CLI tool and initial configuration is a bit more tedious than point and click. I ended up improving musa that time when I used it but after all being setup continues use is all automated.

HOw did you get a scenario to upload using MUSA? I recently tried uploading a scenario and it didn't work because "uploading scenarios isn't supported" because musa can't generate the unique ID's thats require by Banana's for scenarios and scripts. YOu can see my problem going back a couple of posts.

[Zuu]

This was years ago and all I can see is that I've hard coded my uniqueid in make.py which builds the musa ini files:
https://dev.openttdcoop.org/projects/gs ... ke_musa.py

From what I can see the musa version I have around is from 2013. So I see these possible ways it could have happpened:

• either it was possible back then to get the uniqueid using the tools
• or I uploaded the scenario first via BaNaNaS to get a uniqueid
• I read the source code on how to client-side generate the uniqueid or if it is server generated I probably used bananas to do it and then uploaded subsequent updates with advanced dependency support using musa.

Edit: Looking at depgen.py it looks like uniqueid indeed has to be obtained from bananas web manager. I also found this post on depgen.py.

Code: Select all

		elif ext == "scn":
			type = "Scenario"
			md5sum = validate_md5(tar.extractfile(file), None, tar.getmember(file).size)
			uniqueid = '<copy uniqueid from BaNaNaS web UI>' # Scenarios do not carry uniqueid. It has to be obtained from the Bananas server

[stefino_cz]

Hi all, we tried to upload files and musa gave to us this message - something about "connection was end by remote host"

Any idea where is the problem? Thanks

[rowdog]

I can't really comment on musa but I see in the traceback that you were asked to enter "yes I am" but you entered "zes I am".