On 06/11/2017 05:24 PM, David Seifert wrote: >> We can always patch the eclass at that point if that is still a big >> concern, but I fundamentally agree with William on this, starting >> point >> should be fixing it upstream, so can start with a tracking bug on >> affected packages. >> > Here's a deal: you can start filing + fixing them. >
The [tracker] is already started, it was determined to add QA warning with info on filing upstream bugs in [bug 426262] and the proper solution is again iterated in [bug 546614], so its not like this is a new approach that is being suggested, but sure, we should all file bugs when we encounter them. References: [tracker] https://bugs.gentoo.org/show_bug.cgi?id=530632 [bug 426262] https://bugs.gentoo.org/show_bug.cgi?id=426262 [bug 546614] https://bugs.gentoo.org/show_bug.cgi?id=546614 -- Kristian Fiskerstrand OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
