On Mon, Mar 21, 2016 at 12:38:08AM +0100, Gudjon I. Gudjonsson wrote:
> Hi Mattia
> > * you're changing only one binary, what about the others? from what I'm
> > seeing the failure is in the configure step which is done by all
actually, it's in the dh_auto_build for the qt5 one, sorry.
> > binaries, so this change wouldn't fix the FTBFS)
> A mistake. But can I exclude arm only for the qt5 libraries? The qt5 libraries have never been in
> testing so I guess it may be easier.
yes. but now I notice that you restricted the architecture of a qt4
package, which continue to make little sense here.
> Do you know of any package where only the a part is built for all architectures?
none come to my mind.
You could do something similar to this (untested)
define this thing on top of d/rules:
ifneq (,$(findstring qt5, $(shell dh_listpackages)))
BUILD_qt5 := yes
else
BUILD_qt5 :=
endif
the in the various overrides you do something like this:
override_dh_auto_configure:
mkdir -p build-qt4 build-qt5
cp -a doc build-qt4/
QT_SELECT=qt4 dh_auto_configure --builddirectory=build-qt4 -- ../qwtplot3d.pro
if $(BUILD_qt5)
QT_SELECT=qt5 dh_auto_configure --builddirectory=build-qt5 -- ../qwtplot3d.pro
endif
iirc dh_listpackages will not return the qt5 packages if you are
building in an architecture that is not in the Architecture: list of
those packages.
> > * why are you not closing the bug?
> Because it isn't solved. I would prefer to port the code to use GL that works on arm but
> until that is done I will exclude arm.
> I will reduce the bugs severity as soon as version -10 is uploaded.
ok, please consider to not lower it under important, as this is really
an hack.
> > * do you know that to allow the testing migration you'd still need to
> > remove the binaries from unstable by filing a bug against
> > ftp.debian.org? actually that would be enough, even without
> > restricting the architecures where you build, then you can leave the
> > packages in FTBFS state there until it could build again.
> Sorry, I didn't know but that sounds reasonable.
> But if I keep the qt4 binaries in but only restrict the qt5 binaries. Do I then still need to file a bug?
oh, I didn't notice the qt5 binaries are something new.
Well, my suggestion was to completely kick qwtplot3d from armel/armhf
(also otherwise it would still not work). but if you exclude only those
two binaries (that have never built) it's ok, you don't need to do this.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature