okay I might just upload that since I’ve already gone through the usual manual
testing (e.g., the GUI, desktop integration, etc.) that I do for these packages.
Having said that, thanks again both of you.
- Ben.
--
Prof. Benjamin Burton
Computational Geometry & Topology Group
Schoo
Thanks - there is a new upstream release coming hopefully within the next
month, and I will update the build-depends when I push that through.
- Ben.
Hi Adrian,
> A fix for the regina-normal FTBFS with gcc 7 is attached.
Having just uploaded the fix that has been sitting on my hard drive while I was
on holiday all week, I realised that you had also sent in a patch for this
(which of course is the same one-liner as mine).
Apologies for the d
> That leaves the question: what to do with this bug?
FYI, if a rebuild *is* required then I presume it would be a simple rename from
libsource-highlight4 to libsource-highlight4v5; see the (tested) patch below.
I’m happy to NMU this if the maintainer does not have time (which is why the
chang
in the output from “nm -gC”, but someone else
would be better placed than me to give an opinion on whether this is enough for
a rebuild.
- Ben.
--
A/Prof Benjamin Burton
Computational Geometry & Topology Group
School of Mathematics and Physics
The University of Queensland, Australia
close 797292
thanks
Okay, so on further digging I believe the problem was related to mixed versions
of boost-regex. The build failure that was reported in #797292 used a version
of source-highlight that was built against boost 1.55, whereas the
regina-normal build itself was using boost 1.58 i
A/Prof Benjamin Burton
Computational Geometry & Topology Group
School of Mathematics and Physics
The University of Queensland, Australia
> I removed that line :-/
>
Ah.. hmm, okay.
Maybe it's related to the docs? I saw that some kde docs were being
> generated
>
The doxygen docs should still be generated, but the KDE docs are part of the
KDE build, and should be skipped if --disable-kdeui is passed.
Anyway: I'm looking into it n
Hi Lisandro,
Thanks for looking into this.
The build fails after:
>
>
># All good!
>touch configure-stamp
>
> with exit status 2.
>
The problem is the sanity checks in debian/rules, right between configure
and touch configure-stamp. (This verifies that all the necessary bits are
9 matches
Mail list logo
