Hello,

2017-11-12 21:21 GMT+01:00 Michael Tokarev <m...@tls.msk.ru>:
> Control: tag -1 + moreinfo
>
> 12.11.2017 22:14, Héctor Orón Martínez wrote:
>> Source: qemu
>> Version: 1:2.10.0+dfsg-2
>> Severity: normal
>>
>> Dear Maintainer,
>>
>>   Your package fails to satisfy cross build dependency installability due to 
>> glusterfs-common not being installable via multiarch:
>>   * https://bootstrap.debian.net/cross_all/qemu.html
>>   * DebianBug#881526
>>
>>   You might want to consider disabling glusterfs-common build dependency for 
>> the cross build case, otherwise your package seems to cross build fine.
>
> I'm not sure what's the problem here and why this bugreport exists in the 
> first place.
>
> First, what is "the cross build case", which case is that and why should we 
> care about it?

There are efforts to cross build Debian packages from sources, which
might be beneficial for bootstraping new/old architectures among other
use cases.
I think it woud be nice to be able to cross build QEmu (for new comers
better experience) as explained at:
  
http://suihkulokki.blogspot.com/2017/06/cross-compiling-with-debian-stretch.html

> And second, why should we disable some option(s) and build a broken package 
> in case some
> dependent package is buggy?  I think it is better to fix the buggy package 
> than to introduce
> bugs in other packages.

At your consideration, the option is only to be temporarily disabled
*in the cross case* until #881526 gets properly fixed. Due to
glusterfs-common being uninstallable, I was toying with cross build
case and found QEmu disables this option for Ubuntu distribution and
attempted a successful build without this option. In practical means,
that only needs to add a <!cross> tag after build dependency (I could
provide a tested patch if you need). However, we might leave the cross
build dependency in same way as native build and leave this bug open
to track cross buildability of the package.

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Reply via email to