Your message dated Thu, 8 Aug 2019 11:47:50 +0200
with message-id <[email protected]>
and subject line Re: release.debian.org: rustc can only be cross-compiled on
mips; please override "Not built on buildd" blocker
has caused the Debian Bug report #933045,
regarding rustc can only be built for 32-bit mips* by cross-compiling; please
override "Not built on buildd" blocker
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
933045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933045
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Hi, rustc is currently blocked from migration:
https://qa.debian.org/excuses.php?package=rustc
<adsb> no, the issue is
<adsb> Not built on buildd: arch mips binaries uploaded by infinity0
<adsb> Not built on buildd: arch mipsel binaries uploaded by infinity0
<kibi> if in doubt → https://release.debian.org/britney/excuses.yaml look for
source: rustc and verdicts for that stanza.
<infinity0> is that a recent change in policy?
<adsb> it was announced on dda
<adsb> in the most recent release team post there (the one just after release)
<infinity0> i see ok. the reason i do this is because rustc mips builds run out
of memory
<infinity0> they can't be built natively on a mips machine, they have to be
cross-built
<infinity0> how do you guys think i should proceed?
<infinity0> i tried asking buildd a while ago to support cross builds but they
were reluctant to do it
<elbrus> infinity0: please file a bug against release.debian.org to discuss this
<elbrus> not promising anything but that is probably a reason for an exception
<elbrus> apparently not everybody agrees...
<_rene_> infinity0: can't you make it not built with -g or do -g1 or disable
some features on mipsen?
* _rene_ does the -g1 thingy too, for LO
<_rene_> for anything except amd64 (and i386, but I probably should make it for
i386, too, given I also ignore test suite failures there by now...)
<infinity0> _rene_: i've already tried all of those things
<_rene_> mmh, ok
<infinity0> and various other llvm options, it's detailed in some thread on
pkg-rust-maintainers
https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2019-January/004844.html
https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2019-January/004887.html
https://github.com/rust-lang/rust/issues/56888
X
-- System Information:
Debian Release: 10.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'stable'), (300, 'unstable'), (100, 'experimental'),
(1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hi,
On Thu, Jul 25, 2019 at 06:47:47PM -0700, Ximin Luo wrote:
> Hi, rustc is currently blocked from migration:
>
> https://qa.debian.org/excuses.php?package=rustc
>
> <adsb> no, the issue is
> <adsb> Not built on buildd: arch mips binaries uploaded by infinity0
> <adsb> Not built on buildd: arch mipsel binaries uploaded by infinity0
> <kibi> if in doubt → https://release.debian.org/britney/excuses.yaml look for
> source: rustc and verdicts for that stanza.
>
> <infinity0> is that a recent change in policy?
> <adsb> it was announced on dda
> <adsb> in the most recent release team post there (the one just after release)
The policy that checks if a package is built on the buildds is new.
However, the policy that packages must be built natively (NOT cross-built),
even when they are uploaded by maintainers, and that it must be possible to
build packages on the buildds has existed for a very long time. Your upload(s)
violate this.
This makes your uploads RC-buggy.
An exception will not be granted.
Cheers,
Ivo
--- End Message ---
