| 1 |
Hi, |
| 2 |
|
| 3 |
On 5/12/20 6:40 PM, Joonas Niilola wrote: |
| 4 |
> On 5/12/20 8:36 PM, Samuel Bernardo wrote: |
| 5 |
>> My concern was about the others, for instance go-overlay that I have |
| 6 |
>> enabled. |
| 7 |
>> |
| 8 |
>> Should it be possible to run a QA check to create a bug request to |
| 9 |
>> remember the update of those ebuilds in the overlays? |
| 10 |
>> |
| 11 |
>> This would reduce the bug management task when searching for related bugs. |
| 12 |
>> |
| 13 |
> Nothing stops you from doing that, and reporting any issues you find to |
| 14 |
> overlay maintainers. This is probably doable with a single grep. We |
| 15 |
> _cannot_ cater all the overlays. There has been enough time to react. |
| 16 |
> |
| 17 |
> -- juippis |
| 18 |
|
| 19 |
Maybe I understand wrongly, but I had received in the past automatic bug |
| 20 |
reports from Gentoo QA check related to my overlay. My suggestion is to |
| 21 |
use the Gentoo QA to automatically report that, since with the new merge |
| 22 |
with the removal of EGO_VENDOR that would be validated automatically in |
| 23 |
future Gentoo QA check runs over the overlays at overlays.gentoo.org. |
| 24 |
|
| 25 |
Anyway I can do as you suggests. |
| 26 |
|
| 27 |
Thanks |
Archives