Mosè Giordano

Why do you need subtrees/submodules at all if the code is being moved to another package?

My understanding was that the separation was suggested in order to ease maintenance of code and speed up development. I don't see how splitting up the code into multiple packages...

I was talking about compilation latency _after_ loading the package, not precompilation _before_ even using it.

https://buildkite.com/julialang/yggdrasil/builds/7797#018d136e-5e99-499b-a460-7d62227df9f9/620-2148 ``` [18:01:19] aarch64/Gos-linux.c: In function ‘_Uaarch64_local_resume’: [18:01:19] aarch64/Gos-linux.c:147:1: error: x29 cannot be used in asm here [18:01:19] } [18:01:19] ^ [18:01:19] aarch64/Gos-linux.c:41:7: error: ‘asm’ operand has impossible constraints [18:01:19]...

My guess is that you can't open an already opened file? Note that this is failing in the C library CFITSIO underlying this package.

Again, this is failing inside [CFITSIO](https://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html), there isn't much we can do about this unless you can prove this only happens in this package and not in a pure C...

> There are many situations where installing xvfb is not possible, (e.g. HPC). In that case it seems like it is impossible to use Gtk? What error message are you...

Ok, so that's coming from https://github.com/JuliaGraphics/Gtk.jl/blob/881fdce8eb5a8bce2f1a846f79ac7142177e5b2a/src/Gtk.jl#L142-L146 at least now we know what we're talking about. @tknopp any ideas?

Wow, segmentation faults :slightly_smiling_face:

They removed Julia 1.1 while upgrading to 1.2: https://github.com/docker-library/julia/commit/5f637f20522f82f953c69318002820da70d2e3f9 I guess because 1.1 is unmaintained