Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.rc > #336406 > unrolled thread

Bug#1029178: vtk-dicom: autopkgtest failure

Started bySebastian Ramacher <sramacher@debian.org>
First post2023-01-18 23:40 +0100
Last post2023-01-24 00:00 +0100
Articles 7 — 4 participants

Back to article view | Back to linux.debian.bugs.rc


Contents

  Bug#1029178: vtk-dicom: autopkgtest failure Sebastian Ramacher <sramacher@debian.org> - 2023-01-18 23:40 +0100
    Bug#1029178: vtk-dicom: autopkgtest failure Adrian Bunk <bunk@debian.org> - 2023-01-19 08:00 +0100
      Bug#1029178: vtk-dicom: autopkgtest failure Sebastian Ramacher <sramacher@debian.org> - 2023-01-19 09:30 +0100
    Processed: vtk-dicom: diff for NMU version 0.8.14-3.1 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-01-21 23:00 +0100
    Processed: Bug#1029178 marked as pending in vtk-dicom "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-01-22 15:20 +0100
    Bug#1029178: marked as pending in vtk-dicom Étienne Mollier <emollier@debian.org> - 2023-01-22 15:20 +0100
    Bug#1029178: marked as done (vtk-dicom: autopkgtest failure) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-01-24 00:00 +0100

#336406 — Bug#1029178: vtk-dicom: autopkgtest failure

FromSebastian Ramacher <sramacher@debian.org>
Date2023-01-18 23:40 +0100
SubjectBug#1029178: vtk-dicom: autopkgtest failure
Message-ID<FPpg5-1mSo-3@gated-at.bofh.it>
Source: vtk-dicom
Version: 0.8.14-3
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/v/vtk-dicom/30492694/log.gz

autopkgtest [23:14:01]: test autodep8-python3: set -e ; for py in $(py3versions -d 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import vtkdicom; print(vtkdicom)" ; done
autopkgtest [23:14:01]: test autodep8-python3: [-----------------------
Testing with python3.10:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/vtkdicom/__init__.py", line 1, in <module>
    from .vtkDICOM import *
ModuleNotFoundError: No module named 'vtkdicom.vtkDICOM'

Cheers
-- 
Sebastian Ramacher

[toc] | [next] | [standalone]


#336420

FromAdrian Bunk <bunk@debian.org>
Date2023-01-19 08:00 +0100
Message-ID<FPx3X-1rJJ-5@gated-at.bofh.it>
In reply to#336406
On Wed, Jan 18, 2023 at 11:29:35PM +0100, Sebastian Ramacher wrote:
> Source: vtk-dicom
> Version: 0.8.14-3
> Severity: serious
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/v/vtk-dicom/30492694/log.gz
> 
> autopkgtest [23:14:01]: test autodep8-python3: set -e ; for py in $(py3versions -d 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import vtkdicom; print(vtkdicom)" ; done
> autopkgtest [23:14:01]: test autodep8-python3: [-----------------------
> Testing with python3.10:
> Traceback (most recent call last):
>   File "<string>", line 1, in <module>
>   File "/usr/lib/python3/dist-packages/vtkdicom/__init__.py", line 1, in <module>
>     from .vtkDICOM import *
> ModuleNotFoundError: No module named 'vtkdicom.vtkDICOM'

I don't see how this is the fault of the package,
or something the package could easily address.[1]

The package builds a Python C extension against the default Python3 
version only.

The autopkgtest tests this extension against the default Python3 version.

With python3/unstable the autopkgtest is passing:
https://ci.debian.net/packages/v/vtk-dicom/

Testing against a different python3 default fails for obvious reasons.

> Cheers

cu
Adrian

[1] Building a Python C extension against multiple Python3 versions is 
    easy for packages that build nothing else, but usually hard (and 
    rarely done) for packages that build Python bindings for a C/C++
    library as part of their normal build process.

[toc] | [prev] | [next] | [standalone]


#336423

FromSebastian Ramacher <sramacher@debian.org>
Date2023-01-19 09:30 +0100
Message-ID<FPyt4-1sJy-3@gated-at.bofh.it>
In reply to#336420
On 2023-01-19 08:49:00 +0200, Adrian Bunk wrote:
> On Wed, Jan 18, 2023 at 11:29:35PM +0100, Sebastian Ramacher wrote:
> > Source: vtk-dicom
> > Version: 0.8.14-3
> > Severity: serious
> > 
> > https://ci.debian.net/data/autopkgtest/testing/amd64/v/vtk-dicom/30492694/log.gz
> > 
> > autopkgtest [23:14:01]: test autodep8-python3: set -e ; for py in $(py3versions -d 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import vtkdicom; print(vtkdicom)" ; done
> > autopkgtest [23:14:01]: test autodep8-python3: [-----------------------
> > Testing with python3.10:
> > Traceback (most recent call last):
> >   File "<string>", line 1, in <module>
> >   File "/usr/lib/python3/dist-packages/vtkdicom/__init__.py", line 1, in <module>
> >     from .vtkDICOM import *
> > ModuleNotFoundError: No module named 'vtkdicom.vtkDICOM'
> 
> I don't see how this is the fault of the package,
> or something the package could easily address.[1]

python3-vtk-dicom's Depends are incorrect. If it only builds the
extension module, it is supposed to have python3 (>= $default-version),
python3 (<< $default-version + 1) as depenedency. From the buildlog:

dpkg-gencontrol: warning: package python3-vtk-dicom: substitution variable ${python3:Depends} unused, but is defined

Adding the substvar to python3-vtk-dicom's Depends should fix this
issue.

Cheers

> 
> The package builds a Python C extension against the default Python3 
> version only.
> 
> The autopkgtest tests this extension against the default Python3 version.
> 
> With python3/unstable the autopkgtest is passing:
> https://ci.debian.net/packages/v/vtk-dicom/
> 
> Testing against a different python3 default fails for obvious reasons.
> 
> > Cheers
> 
> cu
> Adrian
> 
> [1] Building a Python C extension against multiple Python3 versions is 
>     easy for packages that build nothing else, but usually hard (and 
>     rarely done) for packages that build Python bindings for a C/C++
>     library as part of their normal build process.

-- 
Sebastian Ramacher

[toc] | [prev] | [next] | [standalone]


#336763 — Processed: vtk-dicom: diff for NMU version 0.8.14-3.1

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2023-01-21 23:00 +0100
SubjectProcessed: vtk-dicom: diff for NMU version 0.8.14-3.1
Message-ID<FQu41-caK-3@gated-at.bofh.it>
In reply to#336406
Processing control commands:

> tags 1029178 + patch
Bug #1029178 [src:vtk-dicom] vtk-dicom: autopkgtest failure
Added tag(s) patch.
> tags 1029178 + pending
Bug #1029178 [src:vtk-dicom] vtk-dicom: autopkgtest failure
Added tag(s) pending.

-- 
1029178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029178
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#336860 — Processed: Bug#1029178 marked as pending in vtk-dicom

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2023-01-22 15:20 +0100
SubjectProcessed: Bug#1029178 marked as pending in vtk-dicom
Message-ID<FQJmq-mfa-11@gated-at.bofh.it>
In reply to#336406
Processing control commands:

> tag -1 pending
Bug #1029178 [src:vtk-dicom] vtk-dicom: autopkgtest failure
Ignoring request to alter tags of bug #1029178 to the same tags previously set

-- 
1029178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029178
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#336862 — Bug#1029178: marked as pending in vtk-dicom

FromÉtienne Mollier <emollier@debian.org>
Date2023-01-22 15:20 +0100
SubjectBug#1029178: marked as pending in vtk-dicom
Message-ID<FQJmq-mfa-13@gated-at.bofh.it>
In reply to#336406
Control: tag -1 pending

Hello,

Bug #1029178 in vtk-dicom reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/med-team/vtk-dicom/-/commit/000591b7b3c676a3825eaa55a9d940e5ec737a37

------------------------------------------------------------------------
debian/control: Use ${python3:Depends}

Closes: #1029178
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1029178

[toc] | [prev] | [next] | [standalone]


#336996 — Bug#1029178: marked as done (vtk-dicom: autopkgtest failure)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2023-01-24 00:00 +0100
SubjectBug#1029178: marked as done (vtk-dicom: autopkgtest failure)
Message-ID<FRdXb-FBL-15@gated-at.bofh.it>
In reply to#336406

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 23 Jan 2023 22:54:51 +0000
with message-id <E1pK5iF-005LqB-5D@fasolo.debian.org>
and subject line Bug#1029178: fixed in vtk-dicom 0.8.14-3.1
has caused the Debian Bug report #1029178,
regarding vtk-dicom: autopkgtest failure
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.)


-- 
1029178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029178
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.rc


csiph-web