You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Wed, Dec 04, 2019 at 11:28:10AM -0800, n8v8R wrote:
cross reference downstream https://bugs.gentoo.org/701982 where the issue explained and the reason why being deferred to lodge the issue upstream
In way of the output yes, but apparently it has not been reported that package compilation fails with the GCC option stricter and causing the subsequent QA issue and abort.
Seems I was mistakenly reckoning that the QA check issue stems from the GCC code but apparently it is something implemented by the downstream repo in their ebuild (package) concept. Thus it is a bit unclear why downstream is deferring to upstream.
Closing since it has the potential for a ping pong between upstream (not caused by our code) and downstream's (stricter) QA check implementation.
cross reference downstream https://bugs.gentoo.org/701982 where the issue explained and the reason why being deferred to lodge the issue upstream
The text was updated successfully, but these errors were encountered: