i was cleaning up netpbm when i noticed that the mpeg-tools source code has a
ton of /tmp/ hardcodes
running `make test` for example will create these files everytime:
the mpeg_encode program will use files named:
/tmp/foobar%d (where %d is a number which increments over time starting at 0)
the convert utilities eyuvtojpeg, vidtoeyuv, vidtojpeg, vidtoppm, and eyuvtoppm
all use /tmp/foobar when converting images
ive added mpeg-tools-1.5b-r2 (KEYWORD-ed -* for now) with three patches:
i was able to test the ppm convert utilities, but i have no idea how to test the
jmovie or vid ones ;)
i tested most of the rewritten tests and it produces same results as unpatched
the mpeg-encode patch i really have no idea how to test ...
x86 please test and mark stable.
stable on x86
Amd64 arch team: could you add the ~amd64 keyword to benefit from the update ?
Let's have a GLSA vote while waiting for amd64.
I tend to vote YES.
i'd vote yes too since this can be triggered during by doing `emerge mpeg-tools`
and user has 'FEATURES=test' in make.conf :/
I vote YES too.
Still waiting on amd64 to mark 1.5b-r2 ~amd64
Fwded to vendor-sec, CAN number asked.
This is CAN-2005-3115