You're receiving this bug because the package in Summary has produced _FORTIFY_SOURCE related warnings indicating the presence of a sure overflow in a static buffer. Even though this is not always an indication of a security problem it might even be. So please check this out ASAP. By the way, _FORTIFY_SOURCE is disabled when you disable optimisation, so don't try finding out the cause using -O0. Thanks, Your friendly neighborhood tinderboxer
Created attachment 246610 [details] Build log
Created attachment 250053 [details, diff] Patch to sphinx3-0.6.3.ebuild to fix reported buffer overflows The first overflow is because the code uses strcpy to copy a sequence that is not meant to be null terminated. The sed changes it to use memcpy for this instead. The second overflow is because the code allocates a char[1] to hold a string that is one character plus a null. The sed changes it to be a char[2].
Still valid with 0.8?
