[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1010149: marked as done (vulkan-loader: New upstream release 1.3.211 available)

Your message dated Wed, 28 Sep 2022 13:42:28 +0100
with message-id <YzRBNDUP8z9T/S+A@horizon>
and subject line Re: Bug#1010149: vulkan-loader: New upstream release 1.3.211 available
has caused the Debian Bug report #1010149,
regarding vulkan-loader: New upstream release 1.3.211 available
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.)


-- 
1010149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010149
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: vulkan-loader
Version: 1.3.204.1-2
Severity: wishlist

A new upstream release of vulkan-loader is available. This version is
on a branch named stabilized_release_2022_04 upstream, so perhaps it is
intended to be some sort of LTS branch?

This release adjusts the behaviour of environment variable overrides:

* $VK_ICD_FILENAMES is deprecated (but still works)
* $VK_DRIVER_FILES replaces $VK_ICD_FILENAMES
* VK_ADD_DRIVER_FILES is like $VK_DRIVER_FILES, but prepends to the search
  path instead of completely replacing it
* Similarly, $VK_ADD_LAYER_PATH prepends to the search path for
  explicit layers instead of completely replacing it like $VK_LAYER_PATH

    smcv

--- End Message ---
--- Begin Message --- 
Version: 1.3.211.0-1

On Mon, 25 Apr 2022 at 12:29:53 +0100, Simon McVittie wrote:
> A new upstream release of vulkan-loader is available

This was released.

    smcv

--- End Message ---
Reply to: