Quoting Ansgar Burchardt (2015-12-07 14:50:32)
> Jonas Smedegaard <d...@jones.dk> writes:
>> debian-installer-netboot-images currently violates Debian Policy by
>> fetching debian-installer images over the network during install -
>> see bug#807168.
>>
>> I believe¹ that debian-installer produces those pieces needed by
>> debian-installer-netboot-images, and suspect that providing in a
>> binary package the pieces needed for debian-installer-netboot-images
>> could (at least partially) solve bug#807168.
>>
>> This bug marked important (not wishlist) as bug#807168 is RC.
>
> I don't think its so easy: d-i-n-i are arch:all packages, but need
> binaries for all architectures. To get these as build-dependencies we
> would need cross-arch build-deps which we don't have so far.
>
> Alternatively building a subset of arch:all packages on every
> architecture would also work, but that would require (at least)
> support for the buildd network building arch:all packages on
> package-specific architectures ("Build-Architecture-Indep" might find
> relevant threads).Sorry, but I don't understand the requirement to change infrastructure. I think I understand how such infrastructure change can be beneficial for more complex issues, and then also could serve for a more elegant solution to this issue, but as I see it debian-installer can (today, with current infrastructure) build binary arch-all package debian-installer-netboot-parts-amd64 on amd64, debian-installer-netboot-parts-arm64 on arm64, and so on. What am I missing? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
