Bug#904610: Updates to spirv-headers needed for new vulkan repositories

On Wed, Oct 3, 2018 at 2:56 AM Timo Aaltonen wrote: > On 25.07.2018 19:59, Brett Johnson wrote: > > 2) Added a third level of upstream versioning to represent the number > > of git commits since the latest API version was first created (this > > would make the current up

Bug#907225: Man pages for glslang

--- a/debian/changelog +++ b/debian/changelog @@ -10,6 +10,9 @@ glslang (7.8.2853-2) unstable; urgency=medium * d/lintian: Add glslang-tools lintian override for binary-without-manpage * d/control: Fix Vcs-Git and Vcs-Browser urls + [ Brett Johnson ] + * Add man pages for spirv-remap

Bug#904610: Updates to spirv-headers needed for new vulkan repositories

symlink so upstream packages will build. + * Add semantic version (# of git commits since 1.3) to version string + + -- Brett Johnson Wed, 25 Jul 2018 10:28:30 -0600 + spirv-headers (1.3-1) unstable; urgency=medium * New upstream version. diff --git a/debian/control b/debian/control in

Bug#891582: Dependency missing in vulkan-utils

On Mon, Mar 12, 2018 at 9:48 AM, Timo Aaltonen <tjaal...@debian.org> wrote: > On Mon, 12 Mar 2018, Brett Johnson wrote: > > >>> But vulkan-smoketest runs fine without the dev package. Smoketest and >>> vulkaninfo are useful as a quick way to test

Bug#891582: Dependency missing in vulkan-utils

> > But vulkan-smoketest runs fine without the dev package. Smoketest and > vulkaninfo are useful as a quick way to test the driver and/or the system. The point of this bug is that smoketest crashes if you pass it the "--validate" option, because it can't load the validation layers (which are in

Bug#884865: Response?

On Wed, Mar 7, 2018 at 8:05 AM, Timo Aaltonen wrote: > > > John Kessenich (main maintainer of glslang) is working on coming up with > > a reasonable versioning scheme for it. So until he does that, you may > > want to use a scheme similar to what I did, that will be

Bug#884865: Response?

> On 26.02.2018 21:50, Brett Johnson wrote: > > On Mon, Feb 26, 2018 at 12:25 PM, Timo Aaltonen <tjaal...@debian.org> > wrote: > >> just wondering (again) if glslang should be > >> packaged separately or not. Because now would be the time to do it. > > >

Bug#884865: Response?

into a problem I think you will also run into packaging the LVL repository. I have to run right now, but I'll send you more details later, when I figure out how to get around it. Thanks! On Fri, Mar 2, 2018 at 9:07 AM, Timo Aaltonen <tjaal...@debian.org> wrote: > On 26.02.2018 21:50, Brett John

Bug#890009: vulkan lunarg layers

These layers are found in the LunarG "VulkanTools" repository ( https://github.com/LunarG/VulkanTools). I've already filed ITP #890474 for these layers.

Bug#891582: Dependency missing in vulkan-utils

Package: vulkan Version: 1.0.65.2+dfsg1-1 Severity: serious Justification: 1 The utility "vulkan-smoketest" in the vulkan-utils package depends on layers in the libvulkan-dev package, but there is no dependency. This can be easily verified by running it with the "--validate" option: $

Bug#884865: Response?

On Mon, Feb 26, 2018 at 12:25 PM, Timo Aaltonen wrote: > just wondering (again) if glslang should be > packaged separately or not. Because now would be the time to do it. FWIW, after digging further down this rabbit hole, I think you made the right call by not wanting to

Bug#884865: Response?

On Thu, Feb 15, 2018 at 4:35 AM, Timo Aaltonen wrote: > Looks like latest vulkan changed how it depends on SPIRV, so we'll just > bite the bullet and package glslang and spirv-tools separately instead.. I've got a first draft of these packages done. Also, I think I should

Bug#884865: Response?

On Thu, Feb 15, 2018 at 10:23 AM, Brett Johnson <br...@lunarg.com> wrote: > Would you like me to file ITPs for them? Or are you planning on doing > so right away? Since we're on opposite sides of the pond, and I'm very impatient :D, I went ahead and filed ITPs for glslang (#89055

Bug#884865: Response?

On Thu, Feb 15, 2018 at 4:35 AM, Timo Aaltonen wrote: > Looks like latest vulkan changed how it depends on SPIRV, so we'll just > bite the bullet and package glslang and spirv-tools separately instead.. Yes, past the 1.0.65 tag/branch, the loader/layers repository (as well

Bug#884865: Response?

Excellent, thank you for the update! On Sat, Feb 10, 2018 at 7:55 AM, Timo Aaltonen <tjaal...@debian.org> wrote: > Brett Johnson kirjoitti 09.02.2018 klo 18:50: > > Any chance of a response to this request? If y'all think it's a bad > > idea, or don't want to do it, th

Bug#884865: Response?

Any chance of a response to this request? If y'all think it's a bad idea, or don't want to do it, that's OK, I'll go back to the drawing board and try to figure out some sane way to package/version glslang and spirv-tools independently (although that's going to be difficult, as they don't have

Bug#884865: Patch to add glslang and spirv-tools packages

Tags: patch Attached is a patch to the 10.65.2 package which is my take at implementing this. I just build/install from the external/glslang and external/spirv-tools directories, and include the results in respective packages. I hope it's helpful. diff --git a/debian/control b/debian/control

Bug#886796: Please package upstream tag sdk-1.0.65.2 (ignore previous 1.0.65 tags)

Package: vulkan Severity: normal Previous 1.0.65.* tags had a bug where the testing "Mock" ICD driver was partially installed. This problem has been fixed in upstream 1.0.65.2, so the packaging won't fail on an unaccounted-for .json file left around in /etc/icd.d. -- Brett J

Bug#884865: Working for LunarG

packaging is part of what I'm working on for them. So, I just wanted to add this to the bug, so nobody is confused :) -- Brett Johnson <br...@lunarg.com>

Bug#884865: vulkan: Please include glslang, spirv-tools, and spirv-headers in vulkan source package

stream versioning problems can be worked out), and this could cause a file conflict. It would be better if that potential conflict wasn't hidden inside the libvulkan-dev package, but instead was inside a package which explicitly names glslang and spirv, and could make a clean "conflicts-with"