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

Groups > linux.debian.bugs.rc > #311524

Bug#1001657: Ball fails its autopkgtest - how to properly deal with sip files?

Show all headers | View raw

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

Control: tags -1 - pending
Control: tags -1 + help

Hi Andreas,

Andreas Tille, on 2021-12-14:
> For whatever reason python3-sip did not ended up in the package
> dependencies. Thus I added it explicitly[3].  But the autopkg issue
> remains[4]:
> 
> autopkgtest [17:09:54]: test autodep8-python3: [-----------------------
> Testing with python3.9:
> Traceback (most recent call last):
>   File "<string>", line 1, in <module>
>   File "/usr/lib/python3/dist-packages/BALL.py", line 5, in <module>
>     from BALLCore import *
> ModuleNotFoundError: No module named 'BALLCore'
> autopkgtest [17:09:55]: test autodep8-python3: -----------------------]
> 
> and we have the sip file 
> 
>    /usr/lib/python3/dist-packages/BALL/BALLCore.sip
> 
> I have no idea why this is not found.

Trying to recollect what this was about: the BALLCore.sip
contains a sort of template which must be compiled by several
tools, the first being sip, before being usable by the python3
interpreter.  It is not built initially, due to a cmake file
using an old sip naming convention; see the first hunk in the
patch attached.

However, once the sip file is caught, the package fails to build
from source due to various errors in the generated code.  The
patch also addresses one of them in its second hunk.  I think I
was stuck on some "overrides" related errors, but they were
interleaved within sip output, I can send a proper log later
this week after an overnight build if needed.

Sorry I did not manage to go much further on that issue,
-- 
Étienne Mollier <emollier@emlwks999.eu>
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/1, please excuse my verbosity.

Back to linux.debian.bugs.rc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#1001657: ball: binary-any FTBFS Adrian Bunk <bunk@debian.org> - 2021-12-13 20:50 +0100
  Processed: Re: Ball fails its autopkgtest - how to properly deal  with sip files? "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-12-14 22:00 +0100
  Bug#1001657: Ball fails its autopkgtest - how to properly deal with sip files? Andreas Tille <andreas@an3as.eu> - 2021-12-14 22:00 +0100
    Bug#1001657: Ball fails its autopkgtest - how to properly deal with sip files? Étienne Mollier <emollier@emlwks999.eu> - 2021-12-14 23:00 +0100
  Processed: Re: Ball fails its autopkgtest - how to properly deal  with sip files? "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-12-14 23:00 +0100
  Bug#1001657: Ball fails its autopkgtest - how to properly deal with sip files? Andreas Tille <andreas@fam-tille.de> - 2021-12-15 10:10 +0100
  Bug#1001657: Ball fails its autopkgtest - how to properly deal with sip files? Andreas Tille <tille@debian.org> - 2021-12-16 09:00 +0100
  Bug#1001657: Ball fails its autopkgtest - how to properly deal with sip files? Étienne Mollier <emollier@emlwks999.eu> - 2021-12-16 21:50 +0100
  Bug#1001657: marked as done (ball: binary-any FTBFS) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-12-18 21:40 +0100

csiph-web