On Tue, Jul 17, 2018 at 10:36 PM John Paul Adrian Glaubitz <glaub...@physik.fu-berlin.de> wrote: > > On 07/17/2018 02:29 PM, Aron Xu wrote: > > As a temporary solution to unblock, I've built the package on a > > loongson-3a box and uploaded. It is the same hardware as eberlin.d.o, > > which in turn suggests this could be related to Cavium hardware. > > Unless DSA is willing to blacklist the rustc package on the buildd hardware > where it doesn't build (if that's actually the case), this won't work and > will cause the package to FTBFS if it hits the wrong buildd. > > For Debian Ports, this would be acceptable. Don't know about release > architectures > though. The policy could be different there. >
Binary only upload from porter is allowed but not encouraged, it works similar to an initial upload with source+binary. As said this is temporary, blacklisting is needed and we are just relaxing Rust maintainers from being worried too much about migration. Cheers, Aron
