| 1 |
On 04/30/2016 02:16 PM, Andreas K. Huettel wrote: |
| 2 |
> |
| 3 |
> Hi all, |
| 4 |
> |
| 5 |
> just as a small reminder, to ease the load on all arch teams: |
| 6 |
> |
| 7 |
> If a stablerequest has the keyword ALLARCHES set, then |
| 8 |
> * the first arch that tests successfully and stabilizes |
| 9 |
> * can and *should* immediately stabilize for all requested arches! |
| 10 |
> |
| 11 |
> Whether this keyword is set on a bug is decision of the package maintainer. |
| 12 |
> |
| 13 |
> For example, Perl team sets ALLARCHES normall for all pure-perl packages |
| 14 |
> (i.e., no compilation / gcc involved). |
| 15 |
> |
| 16 |
> Here's an example how this was used: |
| 17 |
> https://bugs.gentoo.org/show_bug.cgi?id=578408 |
| 18 |
> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=44c2d31dfc61bb3e2aee3709cb5a784b213511fa |
| 19 |
> |
| 20 |
> Cheers, Andreas |
| 21 |
> |
| 22 |
> |
| 23 |
|
| 24 |
A package working on one arch won't necessarily guarantee that it works |
| 25 |
correctly on all other arches. Shouldn't we at least make sure we're |
| 26 |
testing on the relevant arch? For example, I don't have any hppa |
| 27 |
hardware. If I stabilized for amd64, why should I stabilize for hppa? I |
| 28 |
can't in good faith claim that it'll work fine for hppa because I've not |
| 29 |
tested it. |
| 30 |
|
| 31 |
As you said, however, it's a choice of the maintainer. Things like Perl |
| 32 |
and Python may be less prone to this issue since they're meant to be |
| 33 |
portable. |
| 34 |
|
| 35 |
My apologies if my concern is misplaced. |
| 36 |
|
| 37 |
~zlg |
| 38 |
-- |
| 39 |
Daniel Campbell - Gentoo Developer |
| 40 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
| 41 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |
Archives