When emergeing sylpheed-claws 0.9.4 (with ACCEPT_KEYWORDS="~x86", of course), the build process commences correctly, configure script runs OK, then at the beginning of the build process you get an error, becase a file sylpheed-claws.pot cannot be found. A quick grep: tar tjf /usr/portage/distfiles/sylpheed-0.9.4claws.tar.bz2 | grep pot |\ grep sylpheed reveals that the required file is called sylpheed.pot. Renaming the file to sylpheed-claws.pot, regenerating the .tar.bz2 archive, rebuilding the digest for the package results in a workable clean ebuild. Reproducible: Always Steps to Reproduce: 1. ACCEPT_KEYWORDS="~x86" emerge sylpheed-claws Actual Results: Error as in "Details" above. Expected Results: Complete build process correctly. Well. Kinda fixed already.
The problem is in these lines: src_unpack() { ... sed -e "s/PACKAGE\=sylpheed/PACKAGE\=sylpheed-claws/" ${i}.orig > ${i} ... } Dont know why that line is necessary because u can change sylpheed programname by " --program-suffix=SUFFIX append SUFFIX to installed program names". Which is in fact added to ebuild! Any problems by removing the "sed" line in ebuild ? -- In fact i dont think it has any usefulness to have both sylpheed and sylpheed-claws installed simultaneously. The whole process could be much easier then. Dont beat me if i am wrong :)
Yes, it works. You remove the lines and you can emerge it. What's more, the executable is called correctly (sylpheed-claws). Can anyone commit the change to the ebuild?
the sed is necessary so that the directories in /usr/lib and /usr/share are called sylpheed-claws too.
genone, I'm assigning to you, but you reason is valid...go ahead and close if you want.
Can't confirm the bug with 0.9.4 or 0.9.5. If you still encounter it please attach a full build log and reopen the bug.
