Qt source download is broken

[mleotta]

Qt source download is broken

[dstoup]

I fixed and merged. We are hosting it on data.kitware.com. Given what you said, glad we did.

…

On Thu, Jan 28, 2021 at 12:15 PM David Russell ***@***.***> wrote: I hit this issue as well, and this Qt blog post <https://www.qt.io/blog/problem-with-open-source-downloads> suggests it was a massive server error with no clear resolution date. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#633 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKEAWSUT2WGXV3KFAWZV3TS4GLUVANCNFSM4WOZSXQQ> .

-- David Stoup Principal Engineer Kitware, Inc. 1712 Route 9, Suite 300 Clifton Park, NY 12065-3104 518-881-4949 (W) 518-312-3946 (M) 518-371-4573 (F)

[dstoup]

Qt is great at keeping their URLs a moving target. It was less than a year ago that @mwoehlke-kitware made the change from archive to new_archive. It does look like 5.11 is gone completely. The options for earlier v5 look like we need to roll back to 5.9.9 or use 5.12. I seem to recall 5.12 being a problem for Vivia though.

I did find a location for 4.8.6-rc2 which we can use, or there is a 4.8.7-rc2 as well. It does make me wonder though, do we still need Qt4? Vivia is likely the only product we have that might still want it for one of its repos but not sure. We probably need @mwoehlke-kitware to chime in here.

[mleotta]

I am hopeful that we can drop Qt4. I don't think I've tested 5.12 with TeleSculptor, but I would be in favor of moving to that as long as there are no significant issues.

Version choices aside. Have we considered mirroring versions of the source packages Fletch uses on a Kitware server, like data.kitware.com? This could be as a fallback. If the official link is unreachable then look at data.kitware.com.

[dstoup]

I was thinking it would be good to host the missing file on data.kitware.com. We host other package files there so I don't think there should be any permission issues. I was on the fence since I prefer getting these things from the source but Qt is such a moving target, it's probably worth doing while we figure out the right versions to use. I will try getting a patch together now and see what happens. I will look for the missing 4.8.6 file as well and do the same if I have a copy of it but really hope we can just drop it.

…

On Mon, Jan 25, 2021 at 12:45 PM Matt Leotta ***@***.***> wrote: I am hopeful that we can drop Qt4. I don't think I've tested 5.12 with TeleSculptor, but I would be in favor of moving to that as long as there are no significant issues. Version choices aside. Have we considered mirroring versions of the source packages Fletch uses on a Kitware server, like data.kitware.com? This could be as a fallback. If the official link is unreachable then look at data.kitware.com. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#633 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKEAWT7O5KMEAPZ7YGK6ULS3WU27ANCNFSM4WOZSXQQ> .

-- David Stoup Principal Engineer Kitware, Inc. 1712 Route 9, Suite 300 Clifton Park, NY 12065-3104 518-881-4949 (W) 518-312-3946 (M) 518-371-4573 (F)

[mwoehlke-kitware]

Qt4 is a @mattdawkins / Arslan question. I haven't touched Qt4 since before COVID, but there are some projects still using ancient ViViA forks. (I don't recall 5.12 being an issue; everything I've done lately has been against 5.15...)

[mwoehlke-kitware]

Also, aren't we already mirroring some of these on data.kitware.com? Conveniently, IIRC 5.12.x is the one that's missing from that; I believe we already have fletch's 4.8.x and 5.11.x.

[mleotta]

Regarding moving to v5.12 as the default, I just tried this option on both Linux and Windows and Qt failed to build in both cases but for different reasons. I'm not the right person to work through those issues. Maybe we should create a "make Qt 5.12 default" branch just to work through the build issues. We could also jump ahead to 5.15 if that makes more sense. Is anyone using 5.12? One we have new version of Qt5 that builds in Fletch I'm happy to test it out in TeleSculptor.

[dstoup]

That's a good idea. The dashboards seem to be a bit of a mess. I will try to push on that today so we can get clean CI.

…

On Mon, Jan 25, 2021 at 9:51 PM Matt Leotta ***@***.***> wrote: Regarding moving to v5.12 as the default, I just tried this option on both Linux and Windows and Qt failed to build in both cases but for different reasons. I'm not the right person to work through those issues. Maybe we should create a "make Qt 5.12 default" branch just to work through the build issues. We could also jump ahead to 5.15 if that makes more sense. Is anyone using 5.12? One we have new version of Qt5 that builds in Fletch I'm happy to test it out in TeleSculptor. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#633 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKEAWWUO4YEFVGLH2GDPEDS3YU4DANCNFSM4WOZSXQQ> .

-- David Stoup Principal Engineer Kitware, Inc. 1712 Route 9, Suite 300 Clifton Park, NY 12065-3104 518-881-4949 (W) 518-312-3946 (M) 518-371-4573 (F)

[russelldj]

I hit this issue as well, and this Qt blog post suggests it was a massive server error with no clear resolution date.

[dstoup]

Fixed in #638

[mattdawkins]

VIAME still uses a little Qt4, though we want to get off it.

[dstoup]

We should be ok for now. I am hosting the Fletch Qt v4 on data,kitware.com to prevent interruptions.

…

On Thu, Jan 28, 2021 at 12:23 PM Matthew Dawkins ***@***.***> wrote: VIAME still uses a little Qt4, though we want to get off it. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#633 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKEAWXZM44Y2HRGKZ5W6LTS4GMPHANCNFSM4WOZSXQQ> .

-- David Stoup Principal Engineer Kitware, Inc. 1712 Route 9, Suite 300 Clifton Park, NY 12065-3104 518-881-4949 (W) 518-312-3946 (M) 518-371-4573 (F)