On Fri, Dec 18, 2020 at 2:27 AM John Paul Adrian Glaubitz <glaub...@physik.fu-berlin.de> wrote: > > On 12/18/20 2:44 AM, Sandro Tosi wrote: > >> It seems that most of the Python dependencies in Build-Depends in > >> debian/control > >> are optional when comparing those with the build dependencies in openSUSE > >> [1]. > > > > they are not: they are either used to run tests or build the documentation. > > Well, that actually means they are optional for building the package. They > should > be marked as <!nocheck> then or <!stage1>
many of these b-d predate the introduction (or wide-spread use) of build profiles and recently introduced b-d are being tagged, so this is an unhelpful comment. > > >> I used the brute-force approach now and it built for me on powerpc with > >> those > >> packages set to <!stage1>: > >> > >> python3-all-dbg, > >> python3-all-dev, > >> python3-cairocffi [!ia64] <!stage1>, > >> python3-certifi (>= 2020.6.20-1) <!stage1>, > >> python3-colorspacious <!stage1>, > >> python3-cxx-dev <!stage1>, > >> python3-cycler (>= 0.10.0) <!stage1>, > >> python3-dateutil <!stage1>, > >> python3-gi <!stage1>, > >> python3-ipython <!nodoc> <!stage1>, > >> python3-ipywidgets <!stage1>, > >> python3-kiwisolver <!stage1>, > >> python3-kiwisolver-dbg <!stage1>, > >> python3-mock <!stage1>, > >> python3-nose <!stage1>, > >> python3-numpy <!stage1>, > >> python3-numpy-dbg <!stage1>, > >> python3-numpydoc <!stage1>, > >> python3-pandas <!stage1>, > >> python3-pil <!stage1>, > >> python3-pkg-resources <!stage1>, > >> python3-pyparsing (>= 1.5.6) <!stage1>, > >> python3-pyqt5 [!hurd-i386] <!stage1>, > >> python3-pytest <!stage1>, > >> python3-scipy <!nodoc> <!stage1>, > >> python3-setuptools, > >> python3-six (>= 1.4) <!stage1>, > >> python3-sphinx <!nodoc> <!stage1>, > >> python3-sphinx-copybutton <!nodoc> <!stage1>, > >> python3-sphinxcontrib.svg2pdfconverter <!nodoc> <!stage1>, > >> python3-tk <!stage1>, > >> python3-tk-dbg <!stage1>, > >> python3-tornado <!stage1>, > > > > this is not good enough, you just marked !stage1 for all the packages > > that were on your way. please rework this patch to mark each of those > > as either !nodoc or !nocheck where appropriate and run the build with > > both profiles disabled; at that point i will be able to merge this. > > As Samuel already pointed out, the main problem is the incorrect use of > the build profile markers. It should be <!nocheck !stage1> not <!nocheck> > <!stage1>. which, btw, you suggested in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954071 > > So, if you could fix this for the time being, we'd already be a step further. are you saying that is the only problematic b-d that prevents matplotlib bootstrap? -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi