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

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

Bug#1001657: ball: binary-any FTBFS

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

Contents

  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

#311451 — Bug#1001657: ball: binary-any FTBFS

Source: ball
Version: 1.5.0+git20180813.37fc53c-9
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=ball&ver=1.5.0%2Bgit20180813.37fc53c-9

...
dh_installdocs
	install -d debian/libball1.5/usr/share/doc/libball1.5
	install -p -m0644 debian/copyright debian/libball1.5/usr/share/doc/libball1.5/copyright
	install -d debian/libball1.5-dev/usr/share/doc/libball1.5-dev
	install -p -m0644 debian/copyright debian/libball1.5-dev/usr/share/doc/libball1.5-dev/copyright
	install -d debian/libballview1.5/usr/share/doc/libballview1.5
	install -p -m0644 debian/copyright debian/libballview1.5/usr/share/doc/libballview1.5/copyright
	install -d debian/libballview1.5-dev/usr/share/doc/libballview1.5-dev
	install -p -m0644 debian/copyright debian/libballview1.5-dev/usr/share/doc/libballview1.5-dev/copyright
	install -d debian/python3-ball/usr/share/doc/python3-ball
	install -p -m0644 debian/copyright debian/python3-ball/usr/share/doc/python3-ball/copyright
	install -p -m0644 debian/copyright debian/ballview/usr/share/doc/ballview/copyright
	install -d debian/ballview/usr/share/doc-base/
	install -p -m0644 debian/ballview.doc-base debian/ballview/usr/share/doc-base/ballview.ballview
find debian/*/usr/share -type d -empty -delete
find debian/*/usr/share -name jquery.js -delete
find debian/*/usr/share -name license.txt -delete
mv debian/libball1.5-data/usr/share/BALL-1.5/BALLView/html debian/libball1.5-data/usr/share/doc/libball1.5-data/BALLView
mv: cannot stat 'debian/libball1.5-data/usr/share/BALL-1.5/BALLView/html': No such file or directory
make[1]: *** [debian/rules:158: override_dh_installdocs] Error 1

[toc] | [next] | [standalone]

#311516 — Processed: Re: Ball fails its autopkgtest - how to properly deal with sip files?

Processing control commands:

> tags -1 pending
Bug #1001657 [src:ball] ball: binary-any FTBFS
Added tag(s) pending.

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

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

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

Control: tags -1 pending

I've fixed the dh_installdocs issue in Git[1] but wanted to solve
the autopkgtest issue as well.  At first I provided the proper
module name[2] which brought me back to the old discussion here:

Am Thu, Sep 23, 2021 at 11:59:50PM +0200 schrieb Étienne Mollier:
> Hi Nilesh,
> 
> Nilesh Patra, on 2021-09-23:
> > The problems that I see on a quick look are:
> > 1) the import name is wrong, it should be BALL instead of ball
> > this is trivial to fix
> > 2) This is the bigger problem. python3-ball is broken, it needed to compile
> > the .sip files, to make an so lib
> > and import that. This is not happening. Probably fixing this is also not
> > hard, just passing SIP_LIBRARY with cmake
> > might do the trick, but again no time.
> > 
> > Also, my understanding is that it was always broken, and has got barely
> > anything to do with my bug fix.
> > Since I am very very short on time, @Etienne, could you please fix this and
> > dput?
> 
> Thanks for drawing my attention on this!  I can have a look,
> sure, although I don't guarantee this will be solved this
> evening; it looks like quite the machine cycles hog.  It is the
> first time I hear about sip, it looks kinda similar to swig.
> Will run an overnight build to see if I can manage to do
> something with the SIP_LIBRARY environment variable; thanks for
> the tip!

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.

Kind regards

       Andreas.


[1] https://salsa.debian.org/med-team/ball/-/commit/451bb880214e04c1042fabd19acef30fbf1ede78
[2] https://salsa.debian.org/med-team/ball/-/commit/129417031797d553a3f87a9de5abfd05d6e848c0
[3] https://salsa.debian.org/med-team/ball/-/commit/df9bd210dd6c172563583bc14278cf3bbc0f047b
[4] https://salsa.debian.org/med-team/ball/-/jobs/2278393

-- 
http://fam-tille.de

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

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

[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.

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

#311525 — Processed: Re: Ball fails its autopkgtest - how to properly deal with sip files?

Processing control commands:

> tags -1 - pending
Bug #1001657 [src:ball] ball: binary-any FTBFS
Removed tag(s) pending.
> tags -1 + help
Bug #1001657 [src:ball] ball: binary-any FTBFS
Added tag(s) help.

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

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

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

Hi Étienne,

Am Tue, Dec 14, 2021 at 11:13:21PM +0100 schrieb Étienne Mollier:
> Étienne Mollier, on 2021-12-14:
> > 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.
> 
> I forgot I had one other patch to address PyString issues, part
> of the ftbfs.  And also forgot to mention that I had to enforce
> -DSIP_LIBRARIES=/usr/lib/python3/dist-packages from the cmake
> call in d/rules.
> 
> In hope this helps,

May be you can simply push your patches to make sure everything is
stored visibly.

What I'm currently wondering is the following:  According to popcon[1]
python3-ball has 2 votes and its only dependency ballview has 10 votes.
This makes no real sense if ballview would really need python3-ball.
I'm wondering how we can find out whether ballview really depends the
Python3 package or whether we can simply drop it.

Upstream does not seem to be active any more but may be Steffen (in
CC) can clarify this.

Kind regards

    Andreas.

[1] https://qa.debian.org/popcon.php?package=ball

-- 
http://fam-tille.de

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

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

Hi Étienne,

Am Wed, Dec 15, 2021 at 11:23:17PM +0100 schrieb Étienne Mollier:
> 
> I pushed my changes leading to these errors, but getting the
> other bugs affecting ball fixed before Christmas might involve
> undoing the setting of SIP_LIBRARIES in d/rules.

Thanks a lot for your investigations.  I do not think we have a real
time limit for ball - but this is a good time to do some polishing in
BTW and if we delay the solution it might become forgotten again.
That's why I'm asking whether the effort to solve the issue is worth
doing compared to simply droping the Python3 package which I consider a
valid solution of the problem.

Kind regards

      Andreas.

-- 
http://fam-tille.de

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

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

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

Hi all,

Nilesh Patra, on 2021-12-16:
> On 12/16/21 1:24 PM, Andreas Tille wrote:
> > Am Wed, Dec 15, 2021 at 11:23:17PM +0100 schrieb Étienne Mollier:
> > > 
> > > I pushed my changes leading to these errors, but getting the
> > > other bugs affecting ball fixed before Christmas might involve
> > > undoing the setting of SIP_LIBRARIES in d/rules.
> > 
> > Thanks a lot for your investigations.  I do not think we have a real
> > time limit for ball - but this is a good time to do some polishing in
> > BTW and if we delay the solution it might become forgotten again.
> > That's why I'm asking whether the effort to solve the issue is worth
> > doing compared to simply droping the Python3 package which I consider a
> > valid solution of the problem.
> 
> Only my opinion:
> 
> Just do this, IMO i.e. drop package. I don't think it is worth spending so much
> time to fix this when we have no real users.
> There is a "possibility" that the popcon score (2) would have come from our us installing it in
> own machines only for testing purposes.
> Upstream is dead as well, so this gives me several green flags to
> proceed with a removal.

I think I agree.  Besides, the package is also heavy to build,
and getting the bindings to work can easily become a time sink.

Kind Regards,
-- 
Étienne Mollier <emollier@emlwks999.eu>
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/tty1, please excuse my verbosity.

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

#311710 — Bug#1001657: marked as done (ball: binary-any FTBFS)

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

Your message dated Sat, 18 Dec 2021 20:34:15 +0000
with message-id <E1mygPH-0009UU-TD@fasolo.debian.org>
and subject line Bug#1001657: fixed in ball 1.5.0+git20180813.37fc53c-10
has caused the Debian Bug report #1001657,
regarding ball: binary-any FTBFS
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.)


-- 
1001657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001657
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