Linux AppImage missing

[cooperised]

Hi,

The 0.18 Linux AppImage link on the FreeCAD download page at https://wiki.freecadweb.org/Download gives a 404, and the gihub page at https://github.com/FreeCAD/FreeCAD/releases/tag/0.18.4 shows assets only for Win32, Win64 and Mac. Is there an AppImage build for the current stable release, and if so, anyone know where it's hiding?

Thanks!
-cooperised

[chrisb]

The page is back, I would recommend anyway to have a look at the ver stable 0.19 prerelease.

[cooperised]

Thanks, I'll take a look at 0.19.

I'm not sure what you mean by "the page is back" though - the link from https://wiki.freecadweb.org/Download (which points to https://github.com/FreeCAD/FreeCAD/rele ... 4.AppImage) is still dead, and there are still no appimage or other Linux binary builds listed on the github 0.18.4 page.

-cooperised

[chrisb]

I'm not sure what you mean by "the page is back" though

I can open https://github.com/FreeCAD/FreeCAD/rele ... g/0.19_pre and download the files from there. Perhaps you have a local issue accessing Github. We have seen this before.

[vocx]

...Perhaps you have a local issue accessing Github.

He's talking about the AppImage for 0.18.4.

[chrisb]

He's talking about the AppImage for 0.18.4.

He wanted to try 0.19 anyway, so why look back?

[sgrogan]

He's talking about the AppImage for 0.18.4.

The problem is the way we have https://github.com/FreeCAD/FreeCAD-AppI ... travis.yml setup.
It packages the 0.18 releases branch in a cron job. It's good if a new tag is created on that branch it will auto deploy. It's bad because it keeps deploying the same build over and over and if there is a fault the working build get's trimmed. (The normal fault is an intermittent time out in Travis that causes the packaging to fail but the old asset is still pruned)

I think I know how to disable updating the stable release, but I might break both the stable and dev release doing this.
I may not be able to fix this in realtime.
So... Is it better to go for it, or wait until I have time to monitor and try to fix more quickly?
These timeout issues are becoming more frequent, I don't know if it's increased traffic or $MS takeover of GitHub or both.

[vocx]

...
So... Is it better to go for it, or wait until I have time to monitor and try to fix more quickly?
...

Personally, I think it's better to keep v0.19 alive rather than v0.18. If you can fix both that's good, but make v0.19 the priority.

And I do think the increased traffic is causing issues.

[sgrogan]

Personally, I think it's better to keep v0.19 alive rather than v0.18. If you can fix both that's good, but make v0.19 the priority.

I think I know how to hack it to just disable the automatic 0.18 builds. We will just need to trigger manual if we have a 0.18.5
But I will most likely break things first try and I don't have a good way to test locally. I'll wait till I can monitor the builds/packaging, probably on the weekend.
I don't see an obvious reason why the stable release is affected more by the timeouts, but they haven't been a problem for the .AppImage.

[jae]

As a new user, here is my one post!

How often does the 0.19 app image update? It looks like the appimageupdatetool is updating, but ends up being the same rev 22492 (as of 25SEP). I dug around a little but decided to post here since I'm in new user jail.

thx.jae.