Blacklisting doesn’t fix the transition block. Once the package is outdated on any of the release architectures, transition is blocked.
> On Jul 20, 2018, at 5:15 PM, YunQiang Su <[email protected]> wrote: > > On Tue, 17 Jul 2018 18:10:14 +0200 John Paul Adrian Glaubitz > <[email protected]> wrote: >> On 07/17/2018 06:03 PM, Ximin Luo wrote: >>> Aron, the next version 1.27.1 is already in binary-NEW so the same issue >>> will block testing migration again, when that gets accepted. >> >> Well, I have to partially take my criticism back. Aron has pointed out on IRC >> that rustc was not yet removed for mips64el, I thought that had happened but >> indeed that wasn't the case, just cargo was removed. >> >> So, his upload didn't really change anything in this regard. >> >>> Earlier you said "Binary only upload from porter is allowed [..]" but I am >>> not sure the other porters have access to a loongson-3a box. Will you >>> continue to run builds of new rustc versions on your box? I think that is >>> the key point here. >> >> DSA could blacklist rustc from being built on buildds other than eberlin >> but I assume they won't agree to applying such a hack. > > I have asked Aurelien to blacklist rustc. > @Aurelien, oh the rustc problem is not about `make', it is about llvm. > >> >> Adrian >> >> -- >> .''`. John Paul Adrian Glaubitz >> : :' : Debian Developer - [email protected] >> `. `' Freie Universitaet Berlin - [email protected] >> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 >> >> > > _______________________________________________ > Pkg-rust-maintainers mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers
