Your message dated Sun, 30 Nov 2025 22:45:51 +0100
with message-id <[email protected]>
and subject line Re: Bug#1117043: transition: vtk9
has caused the Debian Bug report #1117043,
regarding transition: vtk9
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 [email protected]
immediately.)
--
1117043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1117043
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected], [email protected]
Control: affects -1 + src:vtk9
User: [email protected]
Usertags: transition
Hi,
I would like to request a transition slot for vtk9.
The package has been uploaded to experimental and an automatic tracker has been
generated.
I was able to rebuild most Level 2 reverse dependencies, I can provide patches
via NMU.
asl # OK
gdcm # TBD, FTBFS in sid
lammps # OK
liggghts # OK
mia # TBD, FTBFS in sid
odin # OK Simple patch needed
open3d # OK
opencascade # OK Simple patch needed
pcl # OK Simple patch needed
therion # OK
yade # OK
Ben file:
title = "vtk9";
is_affected = .depends ~ /\b(libvtk9\.3|libvtk9\.3\-qt)\b/ | .depends ~
/\b(libvtk9\.5|libvtk9\.5\-qt)\b/;
is_good = .depends ~ /\b(libvtk9\.5|libvtk9\.5\-qt)\b/;
is_bad = .depends ~ /\b(libvtk9\.3|libvtk9\.3\-qt)\b/;
Best
-Dominique
--- End Message ---
--- Begin Message ---
On 2025-10-22 11:26:19 +0200, Emilio Pozuelo Monfort wrote:
> On 22/10/2025 11:02, Adrian Bunk wrote:
> > On Wed, Oct 22, 2025 at 10:25:36AM +0200, Emilio Pozuelo Monfort wrote:
> > > On 20/10/2025 18:39, Dominique Belhachemi wrote:
> > > > > Can you take a look at the autopkgtests regressions? [1]. camitk
> > > > > probably needs
> > > > > to be removed from testing, but I don't know about the rest.
> > > > >
> > > > Please remove them from testing.
> > > > Also, python3-vtk-dicom was rebuilt, but the test framework is still
> > > > using the older version
> > > > python3-vtk-dicom (0.8.17-1+b1) instead of
> > > > python3-vtk-dicom (0.8.17-1+b2).
> > >
> > > Does python3-vtk-dicom (and maybe other python3-vtk9 rdeps) need a
> > > stricter
> > > dependency? From its autopkgtest log:
> > >
> > > 48s Testing with python3.13:
> > > 48s Traceback (most recent call last):
> > > 48s File "<string>", line 1, in <module>
> > > 48s import vtkdicom; print(vtkdicom)
> > > 48s ^^^^^^^^^^^^^^^
> > > 48s File "/usr/lib/python3/dist-packages/vtkdicom/__init__.py", line
> > > 2,
> > > in <module>
> > > 48s from .vtkDICOM import *
> > > 48s ImportError: Initialization failed for vtkDICOM, not compatible with
> > > vtkmodules.vtkCommonCore
> > >
> > > If the vtk python module is changing some kind of ABI, then there should
> > > be
> > > appropriate dependencies on the rdeps so they enforce a compatible
> > > version.
> > > See for example python3-numpy with python3-numpy.*-abi.*
> >
> > This is the old problem that the release team wants smooth transitions,
> > but using different so-versions of a library in a binary is usually
> > not safe.
> >
> > And no, symbol versions won't solve that in all cases.
> >
> > https://ci.debian.net/data/autopkgtest/testing/amd64/v/vtk-dicom/65358838/log.gz
> > 47s Setting up libvtk9.5:amd64 (9.5.2+dfsg2-1) ...
> > 47s Setting up libvtk9.3:amd64 (9.3.0+dfsg1-7) ...
> >
> > The proper fix would be:
> > Package: libvtk9.5
> > Breaks: libvtk9.3
>
> Ah. Indeed, let's not do that.
>
> I have added hints so that hopefully vtk9 can migrate.
The package migrated and the old binaries got removed from testing.
Closing.
Cheers
--
Sebastian Ramacher
--- End Message ---
