[08:36] ricotz: so the lines to install the layers were commented out in the vulkan package [08:37] https://launchpadlibrarian.net/286736001/vulkan_1.0.21.0+dfsg1-1_1.0.21.0+dfsg1-1ubuntu1~gpu16.10.1.diff.gz [08:37] I'm wondering why [08:37] just because [08:39] right :) [08:39] oh but those are just the json files [08:59] and here is why we are not getting the actual layers [08:59] -option(BUILD_TESTS "Build tests" ON) [08:59] -option(BUILD_LAYERS "Build layers" ON) [08:59] +option(BUILD_TESTS "Build tests" OFF) [08:59] +option(BUILD_LAYERS "Build layers" OFF) [09:01] it's disabled because layers need SPIR-V nowadays [09:01] to link against [09:01] the layer lib that is [09:04] tjaalton: and I assume we don't have that? [09:05] (SPIR-V) [09:07] no [09:07] fedora integrates that in the same source, perhaps we could do that [09:10] oh, I might have a look at the Fedora package then [09:10] does the blob need that? [09:10] http://pkgs.fedoraproject.org/cgit/rpms/vulkan.git/tree/vulkan.spec [09:12] I think icculus emailed us about the missing layers [09:13] or somebody who has an account on icculus.org [09:13] who's that? [09:14] ah, porter [09:29] icculus = Ryan C. Gordon [09:29] but this was from trick at icculus.org , so I'm not sure [09:35] this needs to happen on debian too [09:36] just don't know what would be the best approach [09:36] yes, that would be better [09:37] that spec file looks scary as hell [09:37] yeah they get away with that.. [09:37] dunno if anything else would find spir-v useful if it would be packaged [09:43] ah there's glslang too [09:48] yes, so we would need both glslang and spirv-tools in the archive [09:50] apparently, the Vulkan SDK includes them [09:52] right, but they're all moving targets and I think having the runtime in the distro should be enough [09:53] glslang and spir-v have no releases [09:54] do you mean in the same vulkan sources [09:54] ? [09:55] vulkan runtime [09:56] oh [10:03] fedora doesn't package the sdk either [10:14] ricotz: I also went ahead and uploaded 370.28 for Zesty. None of the other supported releases needed it because they were already up-to-date in Yakkety and got copied forward. [10:27] tseliot, tjaalton, thank you for looking into this! [10:27] mamarley, I see, I basically copied the yakkety pocket to zesty already, no need to rebuild them [10:28] Ah, OK. [12:40] anyone know how gdm should be restarted from the console? it just ends up in a restart loop [12:42] looks like it killed the system :P [12:42] essentially [12:54] because the old gdm didn't actually stop [13:25] tjaalton, $ systemctl stop gdm.service [13:28] nope [13:28] didn't work [13:30] running that from a vt doesn't work [13:30] after sudo -s [13:31] the main pid is dead, but the session is still alive in vt1 [13:55] ricotz: If you don't mind me asking, how do you copy forward a package to the same PPA but a newer distro release? Whenever I try to do this, it yells at me for "same version already has published binaries in the destination archive". [13:57] mamarley, copy-with-binaries [13:58] Ah, OK, a binary copy. I guess rebuilding doesn't make much sense at this point since Zesty is still practically the same as Yakkety. [13:59] and rebuilding nvidia-blob makes even less sense, since it isn't actually a build, but just copying [13:59] Indeed. === led-bandit is now known as led-away