| 1 |
I would prefer PPC and for that matter arm (which are no longer security |
| 2 |
supported) going the Non-stable route. This would prevent the need for |
| 3 |
stabilization and everything but @system we can instruct the users to |
| 4 |
use ~ppc. |
| 5 |
|
| 6 |
This would also allow for security to not drop it from security |
| 7 |
supported arches and just follow a more relaxed policy for non-stable |
| 8 |
packages. |
| 9 |
|
| 10 |
For those not familiar, we (security) only need to have the package in |
| 11 |
tree and the vulnerable packages dropped, which is easily accomplished |
| 12 |
by the maintainer with no need for arches to get involved. |
| 13 |
|
| 14 |
Yury German (BlueKnight) |
| 15 |
|
| 16 |
On 5/14/17 8:03 AM, Anthony G. Basile wrote: |
| 17 |
> On 5/14/17 6:38 AM, Michael Weber wrote: |
| 18 |
>> On 05/08/2017 09:13 PM, David Seifert wrote: |
| 19 |
>>> If all of this ends in one big bikeshedding fest again, I will start |
| 20 |
>>> dekeywording packages. Fortunately for me, I won't get any complaints |
| 21 |
>>> (because the arch teams are dead). |
| 22 |
>> formal complaint, powerpc team is alive, and I'm lead. |
| 23 |
>> |
| 24 |
> |
| 25 |
> I defer to the ppc lead's decision on this. While I am okay with |
| 26 |
> dekeywording everything *but* @system for ppc, I prefer keeping ppc |
| 27 |
> keywords. |
| 28 |
> |
Archives