| 1 |
On 02/01/20 23:35, Rolf Eike Beer wrote: |
| 2 |
> Am Freitag, 3. Januar 2020, 00:25:06 CET schrieb Mike Pagano: |
| 3 |
>> On Thursday, January 2, 2020 3:32:12 PM EST Rolf Eike Beer wrote: |
| 4 |
>>>> - Allowed a simple "Add keyword(s) <y..> for package <x>" interface, |
| 5 |
>>>> |
| 6 |
>>>> that intelligently created an issue and a target list, and then once |
| 7 |
>>>> the list was built, constantly ensured the list to be valid, or |
| 8 |
>>>> determined automatically when sub-work was completed and reducing the |
| 9 |
>>>> published list automatically, and then responded to potential issues |
| 10 |
>>>> based on changes in git, ( as opposed to being only triggered when |
| 11 |
>>>> the bug was touched ) |
| 12 |
>>> As someone who does both keywordings and stabilizations regularly on hppa |
| 13 |
>>> and sparc I think I must share a bit of my experiences: |
| 14 |
>> <snip> |
| 15 |
>> |
| 16 |
>> hppa is making us keep old kernels around [1]. Should the kernel team be |
| 17 |
>> doing more to get your attention then CC'ing hppa on all of the kernel |
| 18 |
>> STABLEREQ bugs [2]? |
| 19 |
> I only run vanilla-sources since there are still lot of cache corruption |
| 20 |
> problems in hppa kernels, or whatever makes them flaky. |
| 21 |
> |
| 22 |
> Linux pioneer 5.4.6-parisc64 #1 SMP Fri Dec 27 10:23:09 CET 2019 parisc64 |
| 23 |
> PA8800 (Mako) 9000/785/C8000 GNU/Linux |
| 24 |
> Linux voyager 5.4.6-parisc #1 Fri Dec 27 15:46:43 CET 2019 parisc PA8600 (PCX- |
| 25 |
> W+) 9000/785/C3600 GNU/Linux |
| 26 |
> |
| 27 |
> So _I_ personally would say just drop old kernels, but that is in no way |
| 28 |
> authorative. |
| 29 |
> |
| 30 |
> Eike |
| 31 |
Is it viable at all to test gentoo-sources or would it be better simply to |
| 32 |
unkeyword? |
Archives