Bug#766708: Processed: Re: Bug#766708: breaks multiarch cross building
Helmut Grohne writes ("Bug#766708: Processed: Re: Bug#766708: breaks multiarch cross building"):
> Since it is my interest to not cause more work on Matthias, I will try
> to summarize his POV.
> The most obvious bug is the one mentioned in the patch: #760770
> It is about a bug in the implementation of with_deps_on_target_arch (the
> contended feature).
I think I may not understand what's going on here. In your mail to
the TC, you say:
it was possible to build a gcc cross compiler with different
properties from the default build by setting
with_deps_on_target_arch_pkgs=yes and DEB_CROSS_NO_BIARCH=yes.
You mean setting these as environment variables ? If so then it would
seem that this feature has no direct effect on anyone who is not
trying to use it. Is that correct ?
Of course it does have a maintenance burden on the package maintainer,
which is what Don is asking about.
#760770 shows an element of that but it is immediately obvious from
the initial report that something odd is going on and it contains a
link to #720363 which mentions
https://wiki.debian.org/MultiarchCrossToolchainBuild which talks
abouit the with_deps_on_target_arch_pkgs feature. It doesn't appear
that #760770 has taken a great deal of Matthias's time, although it
did necessitate some bug triage.
Are the maintainers of the disputed features subscribed to the
appropriate packages in the PTS ? Does Matthias welcome help triaging
these bugs ? It seems to me that it would be easy to come up with a
workflow that allowed Matthias to usertag these kind of bugs and hand
them over to the cross teams.
> Other bugs that may be relevant here are the ones that Matthias filed
> against cross-gcc-4.9-* (packages that make use of
> with_deps_on_target_arch). These are:
> armhf: #766619 #766626
What are the cross-gcc-4.9-armhf packages that are referred to ?