Re: Issues updating planes located in FGAddon

I am once again asking if we can move to another place (not SF) or move to git submodules...

Half the time I try to push updates to my planes, I get some sort of error (timed out 504) or other strange problems... it is also VERY slow, taking minutes to upload small files, (when git uploads them in < 10 sec to GitHub) and then browsing the entire repo on SF is unavailable for several minutes. This seems to only happen when uploading releases - changing just a few files, no problem. But if I try to commit a new plane or make a new release that touched many files, the I get "expletive"-type behavior.

I'm really getting sick and tired of this. Working with FGAddon shouldn't be so frustrating. It would be so cool to have some sort of modern workflow that doesn't feel so ancient and fragile.

SVN tells me my local copy is out of date, apparently someone touched the MD-80 without talking to me, and well, now as usual I can't even go look because it's doing... something?

See:
[cid:842690d7-f8a8-4bc4-92f6-efa172dfdedd]

Kind Regards,

--
Josh Davidson
________________________________
From: James Turner <[email protected]>
Sent: Monday, January 19, 2026 15:54
To: FlightGear developers discussions <[email protected]>
Subject: Re: [Flightgear-devel] Issues updating planes located in FGAddon



On 19 Jan 2026, at 20:06, Adrián Fernández <[email protected]> wrote:

Confirmed with the c152, thath the update process is OK. The update came out today and worked correctly.

I just need to recover c170b, which has disappeared from FGAddon. I imagine it will reappear once the issue with the Python module is resolved.

I’m having to re-create the SVN checkouts (for all three branches, what fun) to resolve this, on the machine that runs the updates. I did one run earlier but it used the outdated scripts from yesterday, I’ll trigger another run overnight and hope this time it’s using the fixed scripts. At that point all the aircraft which got dropped, should automatically come back and update again.

Separate, we do need someone to help surface the errors - all the warnings, etc from the script have been present since ‘forever’, Florent’s change jsut accidentally made them fatal rather than warnings :)

Kind regards,
James

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel