We really shouldn't have any binary files in the tree. Luckily, we don't have many for our packages :) ./k3d/files/k3d-0.2.5.4-gentoo.patch.tar.bz2 ./xv/files/xv-3.10a-bmpfix.patch.bz2 ./xv/files/xv-3.10a-yaos.dif.bz2 ./yafray/files/yafray-gcc34-fix.gz That first one is going to have to be punted out onto the mirrors and hosted on one of our dev space's as a fallback since uncompressed its 54k. The other 3 are small enough to stay in the tree uncompressed. If no one screams, or does it first, I'll go ahead and fix all of these within the next few days.
Created attachment 68632 [details, diff] xv-3.10a-r11.ebuild.diff I sent all patches to mirrors and put them in http://dev.gentoo.org/~vanquirius/files. k3d and yafray are fixed. xv, however, belongs to taviso and has no herd associated with.
Another thing regarding xv: If bmpfix and yaos fix various security issues, how come -r11 has them and -r12 does not? Doesn't that leave ~arch users exposed?
taviso: could we please punt those binary files out to the mirrors?
blubb resolved this already.
