I'm not sure if phpBB was broken by changes to the apache ebuilds, but it was broken non the less. The ebuild was expecting /etc/apache/conf/apache.conf as the naming and location of the conf. If it wasn't there it checked if the string was NULL and would check /etc/apache2/conf/apache.conf. The string wasn't returning NULL and the ebuild continued to default HTTPD_ROOT to /home/httpd/htdocs. Thats fine because thats where my htdocs is. But, the ebuild then checked to see if HTTPD_ROOT/phpbb was a symbolic link?! Anyway, its a directory, not a symbolic link, so the emerge continues and ultimatley skips the ewarns and die about unmereging older versions first. My fix checks /var/db/pkg/net-www for apache and names the locations correctly. It also checks HTTPD_ROOT/phpbb for directory, not symbolic link. Also defaults to /home/httpd/htdocs and produces a warning if this has to happen. Moved the detection stuff inside pkg_config aswell. Reproducible: Always Steps to Reproduce:
Created attachment 14870 [details, diff] phpBB-2.0.5.ebuild.patch
anyone going to admit responsibility for phpBB?
Patch looks reasonable. Robin - you mind if I test and commit? phpBB is *your* package (grin). Stu
Stu - actually I just bumped it's version to deal with a serious security problem it had. If you want it, it's yours.
Thanks Robin. I'll handle this patch when I get up in the morning.
Okay, I've ported phpBB-2.0.5's ebuild to use the new webapp-apache.eclass that I've added to portage. The idea behind your patch is part of the new eclass, and you're credited in the comments at the top. Please resync and retest. You'll need v1.2 of the ebuild to pick up the fix. Best regards, Stu
closing old bugs.
