that's three time i sent a working boson ebuild that gets badly integrated. I do tests and send something that works, you change it so that it does not work, you probably don't test it (else you would notice it fails), and you put it in the tree. the last one boson-0.6.1-r2.ebuild is even worse : you put an files/digest with a file that boson-0.6.1-r2 does not even use. from boson-0.6.1-r2.ebuild : SRC_URI="http://orzel.freehackers.org/download/boson-all-0.6.1-fixed.tar.bz2" my boson/files/digest-boson-0.6.1-r2 MD5 a8a1f40fde64d5e03d22b3d10cc16198 boson-all-0.6.1-fixed.tar.bz2 27920415 the one you put instead : MD5 ee1571120c461787004e869f08fce8e2 boson-all-0.6.1.tar.bz2 28333742 i really don't know what to do. is that really worth i do the ebuild and tests for that ? i mean, if you want to change something, TEST it, and/or come to talk with me, i'm on irc #boson / openproject almost everytime. i'm open to talking, but i dislike those blind-stupid changes the RIGHT ebuild is on http://orzel.freehackers.org/gentoo if you ever wonder
really strange, i have a scritp that generate the digest for me, sueky my script have a bug. And yes, i tesy all ebuilds that i upload with 3 methods, simply i have a error with digest. sorry for all. and what you refer to stupid changes?
i'm sorry being upset, i don't mean to have crude words. things that went wrong : i did the first ebuild, that get overwritten by a totally wrong ebuild (bad dependencies, way of compiling, and it was not working) then i did a new one (due to a bug in our release), and the digest get changed, hence this one was not usable neither i did a new one, changing the name file so that digest/distfiles don't get confused and again, the digest was not only changed, but also the file name ok, what do we do now ? The right md5 is in my tarball. is is too late for -r2 ? should i do a -r3 and upload a 0.6.1-fixed2.tgz somewhere ?? what about irc ? we could go quicker than with bugzilla
