rejects source uploads for existing packages when there are no buildable architectures
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Celso Providelo |
Bug Description
I just got this rejection message from Soyuz:
Rejected:
Cannot build any of the architectures requested: arm mipsel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 14 Oct 2008 14:07:59 +0100
Source: partman-ext2r0
Binary: partman-ext2r0
Architecture: source
Version: 1.15ubuntu1
Distribution: intrepid
Urgency: low
Maintainer: Ubuntu Installer Team <email address hidden>
Changed-By: Colin Watson <email address hidden>
Description:
partman-ext2r0 - Add to partman support for old ext2 (revision 0) (udeb)
Launchpad-
Changes:
partman-ext2r0 (1.15ubuntu1) intrepid; urgency=low
.
* check.d/
- Make $RET look for a boolean value (thanks, Nicolas Valcárcel;
LP: #256459).
[...]
Although I can understand why you added this check, this seems wrong for two reasons:
1) It's already in the archive. We shouldn't have packages in the archive that there is no way to upload.
2) This impedes our ability to prepare for forthcoming architecture additions. We expect to be adding armel in Ubuntu 9.04, and it would be valuable to upload armel-specific packages in preparation for this. As it happens, partman-ext2r0 is only built for (big-endian) arm at present, but depending on bootloader requirements I could well imagine that it could be useful on armel too. (Thus I would rather not resolve 1) simply by removing packages that we can't currently build.)
Changed in soyuz: | |
assignee: | nobody → cprov |
importance: | Medium → High |
milestone: | pending → 2.1.11 |
status: | Triaged → In Progress |
Changed in soyuz: | |
milestone: | 2.1.11 → 2.1.12 |
Changed in soyuz: | |
status: | Fix Committed → Fix Released |
That seems a fair rationale to me, unless Celso has anything to add?