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

Bug#927859: marked as done (unblock: vulkan-validationlayers/1.1.101.0-1)

Your message dated Sun, 5 May 2019 14:18:16 +0200
with message-id <20190505121815.zuyjc3avlobf5kki@debian.org>
and subject line Re: unblock: vulkan-loader/1.1.101.0-2, vulkan-validationlayers/1.1.101.0-1, glslang/7.11.3113-1
has caused the Debian Bug report #927859,
regarding unblock: vulkan-validationlayers/1.1.101.0-1
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.)


-- 
927859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927859
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package vulkan-validationlayers

This was supposed to get in testing before the freeze, but apparently the cutoff date was practically a few days earlier than the announced freeze date.

The full diff is too big to paste, but the packaging changes are here:

diff -Nru vulkan-validationlayers-1.1.97/debian/changelog vulkan-validationlayers-1.1.101.0/debian/changelog
--- vulkan-validationlayers-1.1.97/debian/changelog     2019-01-19 10:14:16.000000000 +0200
+++ vulkan-validationlayers-1.1.101.0/debian/changelog  2019-03-12 11:37:05.000000000 +0200
@@ -1,3 +1,11 @@
+vulkan-validationlayers (1.1.101.0-1) unstable; urgency=medium
+
+  * New upstream release.
+  * watch: Use proper tag names.
+  * control: Bump glslang-dev and spirv-tools build-depends.
+
+ -- Timo Aaltonen <tjaalton@debian.org>  Tue, 12 Mar 2019 11:37:05 +0200
+
 vulkan-validationlayers (1.1.97-2) unstable; urgency=medium
 
   * copyright: Updated. (Closes: #919686)
diff -Nru vulkan-validationlayers-1.1.97/debian/control vulkan-validationlayers-1.1.101.0/debian/control
--- vulkan-validationlayers-1.1.97/debian/control       2019-01-13 20:05:07.000000000 +0200
+++ vulkan-validationlayers-1.1.101.0/debian/control    2019-03-12 11:36:37.000000000 +0200
@@ -4,14 +4,14 @@
 Uploaders: Timo Aaltonen <tjaalton@debian.org>
 Build-Depends: debhelper (>= 11),
  cmake,
- glslang-dev (>= 7.10.2984),
+ glslang-dev (>= 7.11.3113),
  libvulkan-dev (>= 1.1.97),
  libwayland-dev,
  libx11-dev,
  libxrandr-dev,
  pkg-config,
  python3,
- spirv-tools (>= 2019.1),
+ spirv-tools (>= 2019.2),
 Standards-Version: 4.2.0
 Section: libs
 Homepage: https://github.com/KhronosGroup/Vulkan-ValidationLayers
diff -Nru vulkan-validationlayers-1.1.97/debian/watch vulkan-validationlayers-1.1.101.0/debian/watch
--- vulkan-validationlayers-1.1.97/debian/watch 2019-01-13 19:37:43.000000000 +0200
+++ vulkan-validationlayers-1.1.101.0/debian/watch      2019-03-07 16:06:35.000000000 +0200
@@ -1,3 +1,3 @@
 version=4
-opts="repack,filenamemangle=s/(?:.*?)?v?(\d[\d.]*)\.tar\.gz/vulkan-validationlayers-$1.tar.gz/" \
- https://github.com/KhronosGroup/Vulkan-ValidationLayers/tags (?:.*?/)v(\d[\d.]*)\.tar\.gz
+opts="repack,filenamemangle=s/(?:.*?)?sdk[_-]?(\d[\d.]*)\.tar\.gz/vulkan-validationlayers-$1.tar.gz/" \
+ https://github.com/KhronosGroup/Vulkan-ValidationLayers/tags (?:.*?/)sdk[_-](\d[\d.]*)\.tar\.gz


unblock vulkan-validationlayers/1.1.101.0-1

--- End Message ---
--- Begin Message --- 
Hi,

On Wed, Apr 24, 2019 at 11:16:04AM +0300, Timo Aaltonen wrote:
> This was supposed to get in testing before the freeze, but apparently the
> cutoff date was practically a few days earlier than the announced freeze
> date.

This is incorrect. Please read the freeze policy

https://release.debian.org/buster/freeze_policy.html

The soft freeze started 2019-02-12. At that point "only small, targeted fixes
are appropriate for buster". Your upload wasn't appropriate from that point
on.

The full freeze started 2019-03-12. The migration delay was 10 days since the
start of the soft freeze. So your upload from 07 Mar 2019 wouldn't have
migrated before that. Your upload of 12 Mar 2019 obviously wouldn't have
migrated before that either.

> The full diff is too big to paste, but the packaging changes are here:

These changes are inappropriate. They will not be unblocked.

Ivo

--- End Message ---
Reply to: