control: tag -1 + pending

Dear maintainer,

On 2023-08-21 14:33, Aurelien Jarno wrote:
> On 2023-06-14 09:32, Matthias Klose wrote:
> > Package: src:vtk9
> > Version: 9.1.0+really9.1.0+dfsg2-5
> > Severity: normal
> > Tags: sid trixie
> > User: debian-...@lists.debian.org
> > Usertags: ftbfs-gcc-13
> > 
> > [This bug is targeted to the upcoming trixie release]
> > 
> > Please keep this issue open in the bug tracker for the package it
> > was filed for.  If a fix in another package is required, please
> > file a bug for the other package (or clone), and add a block in this
> > package. Please keep the issue open until the package can be built in
> > a follow-up test rebuild.
> > 
> > The package fails to build in a test rebuild on at least amd64 with
> > gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
> > severity of this report will be raised before the trixie release.
> 
> The following upstream patch fixes the issue:
> https://gitlab.kitware.com/vtk/vtk/-/commit/1233ceec268d5366c66f5e79786ec784042b591b
> 

I've prepared an NMU for vtk9 (versioned as 9.1.0+really9.1.0+dfsg2-6.1)
to fix this FTBFS, you will find the corresponding diff attached. I have
uploaded it to DELAYED/2. Please feel free to tell me if I should delay
it further or cancel it.

Regards,
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurel...@aurel32.net                     http://aurel32.net
diff -Nru vtk9-9.1.0+really9.1.0+dfsg2/debian/changelog vtk9-9.1.0+really9.1.0+dfsg2/debian/changelog
--- vtk9-9.1.0+really9.1.0+dfsg2/debian/changelog	2023-06-22 05:14:50.000000000 +0000
+++ vtk9-9.1.0+really9.1.0+dfsg2/debian/changelog	2023-08-21 21:27:16.000000000 +0000
@@ -1,3 +1,12 @@
+vtk9 (9.1.0+really9.1.0+dfsg2-6.1) unstable; urgency=medium
+
+  [ Aurelien Jarno ]
+  * Non-maintainer upload.
+  * Backport patch from upstream to fix GCC 13 compatibility. (Closes:
+    #1037887).
+
+ -- Aurelien Jarno <aure...@debian.org>  Mon, 21 Aug 2023 23:27:16 +0200
+
 vtk9 (9.1.0+really9.1.0+dfsg2-6) unstable; urgency=medium
 
   * Team upload.
diff -Nru vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/130_gcc13.patch vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/130_gcc13.patch
--- vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/130_gcc13.patch	1970-01-01 00:00:00.000000000 +0000
+++ vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/130_gcc13.patch	2023-08-21 21:12:28.000000000 +0000
@@ -0,0 +1,34 @@
+From 1233ceec268d5366c66f5e79786ec784042b591b Mon Sep 17 00:00:00 2001
+From: Laurent Rineau <laurent.rin...@cgal.org>
+Date: Tue, 17 Jan 2023 16:18:53 +0100
+Subject: [PATCH] Add #include <cstdint> to compile with gcc13
+
+The `vtkSEPReader` was introduced by MRs !4909 (from my former
+collaborator Maxime) and !4938. Then it was highly modified by
+!7516. The later MR is the one that introduced the uses of
+`std::uint8_t` and `std::uint32_t`.
+
+Those types needs the inclusion of `<cstdint>`.
+---
+ IO/Image/vtkSEPReader.h | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+diff --git a/IO/Image/vtkSEPReader.h b/IO/Image/vtkSEPReader.h
+index a7d8aad1510..37d0c44d18c 100644
+--- a/IO/Image/vtkSEPReader.h
++++ b/IO/Image/vtkSEPReader.h
+@@ -25,8 +25,9 @@
+ #include "vtkImageAlgorithm.h"
+ #include "vtkNew.h" // for ivars
+ 
+-#include <array>  // for std::array
+-#include <string> // for std::string
++#include <array>   // for std::array
++#include <cstdint> // for std::uint8_t and std::uint32_t
++#include <string>  // for std::string
+ 
+ namespace details
+ {
+-- 
+GitLab
+
diff -Nru vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/series vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/series
--- vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/series	2023-06-22 05:12:22.000000000 +0000
+++ vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/series	2023-08-21 21:25:56.000000000 +0000
@@ -12,3 +12,4 @@
 99_fix_ftbfs.patch
 110_vtk9_netcdf.patch
 120_fix_shader_crash.patch
+130_gcc13.patch

Attachment: signature.asc
Description: PGP signature

Reply via email to