Bug#1003042: marked as done (Why aren't non-SDK releases packaged?)
Your message dated Sun, 9 Jan 2022 17:25:42 +0200
with message-id <4575c62f-cf39-f1a7-7d3d-b393cc39bca2@tambre.ee>
and subject line Re: Bug#1003042: Why aren't non-SDK releases packaged?
has caused the Debian Bug report #1003042,
regarding Why aren't non-SDK releases packaged?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1003042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003042
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: vulkan-validationlayers
Version: 1.2.189.0-1.1
Severity: wishlist
It seems that debian/watch only tracks tags starting with "sdk-" and
intermediate releases aren't packaged.
Are there any reasons besides time and manpower? Would there be a way to assist?
Lack of timely releases in downstream distros such as Debian is a pain point I
brought up in the LunarG Vulkan 2021 ecosystem survey. My impression was that
this was due to lack of official releases/tags for intermediate versions, but
they have got back to me and pointed out that that is not the case. And indeed I
cannot see any difference between SDK and non-SDK tags besides the SDK ones
having an official binary release from LunarG.
--- End Message ---
--- Begin Message ---
Understandable, thank you!
--- End Message ---
Reply to: