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