As it needs to be dropped due bug 421717 Reproducible: Always
Not sure I follow. I can understand the need to mask cuneiform, but why is it necessary to drop support in other apps? The overflow cannot end up on anybody's system unless they unmask it. The flag can certainly be non-default to avoid pulling in a masked dependency.
If cuneiform will be removed, yagf will not be able to depend on it, or am I missing anything? :/
(In reply to Pacho Ramos from comment #2) > If cuneiform will be removed, yagf will not be able to depend on it, or am I > missing anything? :/ According to ebuild, yagf has an OPTIONAL dependency on cuneiform via 'cuneiform' USE-flag. I think that just masking this USE-flag will do the trick :-) Default OCR engine for yagf in Gentoo is tesseract, so it would not be a problem. P.S. By the way - it has been already masked: # Richard Freeman <rich0@gentoo.org> (24 Mar 2013) # Dependency is masked for buffer overflows for now app-text/yagf cuneiform So, i close this as WONTFIX for now. If app-text/cuneiform will be a candidate for lastrite, please reopen.
(In reply to Sergey Popov from comment #3) > So, i close this as WONTFIX for now. If app-text/cuneiform will be a > candidate for lastrite, please reopen. It is (treecleaners are CCed to clean it)
(In reply to Pacho Ramos from comment #4) > (In reply to Sergey Popov from comment #3) > > So, i close this as WONTFIX for now. If app-text/cuneiform will be a > > candidate for lastrite, please reopen. > > It is (treecleaners are CCed to clean it) It was a treecleaner candidate. It is not at present, though that may change in the future. It is not currently masked for removal, but rather it is masked with the hope that the issue can be fixed...